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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds valuable behavioral context beyond annotations: keyword search returns up to 10 items as summaries only and may be incomplete, while identifier search is more reliable and compact.

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?

Front-loads the purpose and then the key usage advice in a compact two-sentence structure. There is minor redundancy in repeating 'prefer identifiers' at the end, but overall the text is appropriately sized and every sentence carries useful information.

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?

Covers the main search behavior and output limitations (10 summaries, possibly incomplete) well, which is helpful since no output schema exists. However, it omits context for account_id (multi-outpost selection) and identifierType, leaving the agent with gaps for a 4-parameter tool.

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 only 25%, so the description must compensate and partly does: it explains the identifiers parameter (ASIN/EAN/ISBN) and the behavior of keywords. But it leaves account_id and identifierType unexplained, so there is still a meaningful semantics gap.

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 the Amazon catalog.' The purpose is clear, but the description does not distinguish this tool from sibling catalog tools like get_catalog_item or audit_catalog_quality, so it falls short of full sibling differentiation.

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?

Gives explicit guidance on when to prefer identifier search over keyword search (use ASIN/EAN/ISBN for reliable, compact results) and warns that keyword search may be incomplete. However, it does not address when to use this tool versus other catalog-related siblings.

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