search_buyking_semantic_US

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the regional scope, currency, language, and inventory coverage, but does not describe result volume, ordering, pagination, or any limitations such as coverage gaps. For a search tool this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, information-dense, and front-loaded with the most important discriminator ('USA Only'). Every sentence earns its place: scope, pricing/language, when to use, and coverage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple search-tool shape, complete schema documentation, and no output schema, the description covers the key contextual needs: region, currency, language, and delivery scope. It could additionally describe the output format or result limit, but nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the parameter descriptions already explain keyword extraction, sort values, category usage, and platform constraints. The tool description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a concrete verb and resource: search hot deals deliverable within the United States. It clearly distinguishes itself from regional siblings by front-loading '[USA Only]' and stating USD pricing and English results. This lets an agent select it confidently over search_buyking_semantic_KR or _JP.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool: when the user is in the US or wants US-deliverable products. It does not explicitly name alternative regional tools or give exclusion criteria, but the regional usage condition is clear enough given the sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.