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

Beyond the readOnlyHint=true and destructiveHint=false annotations, the description reveals that recommendations are never auto-applied, should be combined with break-even math, and that pagination uses next_token until truncated is absent. This adds meaningful operational context that an agent cannot infer from the schema or annotations alone.

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?

Three dense sentences carry the core purpose, usage guardrail, and pagination caveat in front-loaded order. Every clause adds useful information without fluff or repetition of schema fields.

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?

For a read-only recommendations tool with 7 optional parameters and no output schema, the description covers what the tool returns, how to treat the data, how to act on it, and how paging works. This is sufficient for an agent to select and invoke the tool correctly.

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 71%, and the description enriches parameter understanding by listing example recommendation types (KEYWORD_BID, CAMPAIGN_BUDGET, etc.) and mentioning marketplaces SP/SB/SD that map to ad_products. It also explains the role of next_token in pagination, going beyond the bare schema definition.

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 names a specific resource ('Amazon's own consolidated recommendations / unified Recommendations API') and enumerates the exact kinds of suggestions it returns (bid/budget/bidding-strategy, new keywords, negatives, targets, placement, state) across SP/SB/SD. This clearly distinguishes it from sibling tools like ppc_bid_recommendations or ppc_optimization_suggestions by framing it as the unified read-only source.

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?

The description gives explicit usage guidance: treat as ONE input alongside break-even math, never auto-apply, and act via the stage_* tools. It does not name specific sibling alternatives or spell out when to choose this over ppc_bid_recommendations or ppc_optimization_suggestions, but the directive is actionable and prevents misuse.

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