AWS nova documentation change
Summary
Minor wording changes: added 'currently' to clarify toolChoice support and updated region name format
Security assessment
Changes are purely editorial with no security implications
Diff
diff --git a/nova/latest/userguide/tool-use-definition.md index f7ded7348..516c16c41 100644 --- a/nova/latest/userguide/tool-use-definition.md +++ b/nova/latest/userguide/tool-use-definition.md @@ -13 +13 @@ To define a tool, you create a tool configuration that is passed along with the -Amazon Nova only supports the `auto` option for `toolChoice`, which is the default. Trying to set `any` or specific tool names will cause a validation error. +Amazon Nova currently only supports the `auto` option for `toolChoice`, which is the default. Trying to set `any` or specific tool names will cause a validation error. @@ -47 +47 @@ The name, description, and the input schema must be explicit with the exact func -Amazon Nova understanding models support only a subset of JsonSchema functionality when used to define the [ToolInputSchema](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_runtime_ToolInputSchema.html) in Converse API. +Amazon Nova understanding models currently support only a subset of JsonSchema functionality when used to define the [ToolInputSchema](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_runtime_ToolInputSchema.html) in Converse API. @@ -64 +64 @@ Here is an example of calling a tool with the Converse API: - client = boto3.client("bedrock-runtime", region_name="US East (N. Virginia)") + client = boto3.client("bedrock-runtime", region_name="us-east-1")