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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-call profile is covered. The description adds little beyond a restatement of required params and an implementation hint ('OpenAPI: searchAmazon'); it says nothing about result volume, the limit cap, or how results are ranked.

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?

Two short sentences with the core action and the mandatory-parameter warning front-loaded. The 'OpenAPI: searchAmazon' fragment is tacked on and doesn't help an agent decide or invoke, but it costs little.

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?

Seven parameters and no output schema, yet the description never characterizes the return (list of products? ASINs? prices?) nor the interaction between q and the enum filters. For a search tool with annotations covering safety, this is adequate but leaves real gaps.

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 coverage is 57%, and the schema itself documents q, locale, and marketplace, plus enums for occasion and giftCategory. The description only echoes that marketplace and locale are mandatory, adding no meaning for subject, limit, or the enum semantics. Baseline 3 fits given partial schema coverage.

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?

States a specific verb and resource: 'Search Amazon for teacher appreciation gifts.' The OpenAPI pointer ('searchAmazon') confirms the operation. It does not explicitly distinguish itself from siblings like get_catalog or resolve_product, which an agent could easily confuse with a product search.

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?

'ALWAYS pass marketplace + locale' is a calling instruction, not a when-to-use rule. There is no guidance on when to pick this over get_catalog or resolve_product, and no exclusions or prerequisites are mentioned; usage must be inferred from the name.

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