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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real operational context beyond that: the 20-60 second runtime and the retention note that only summary results are stored, plus the fact that it fetches externally. No auth or rate-limit details, but the latency and storage disclosures are genuinely useful.

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?

Five short sentences, each carrying distinct information: action, return contents, accepted formats, latency, storage. Front-loaded with the action and no filler.

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?

With no output schema, the description carries the burden of describing returns and does so concretely (score, gaps with affected share, unanswerable questions, thinnest products, fix link). Combined with accepted formats and runtime, an agent has everything needed to call it 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 100%, so the baseline is 3, but the description adds format semantics the schema omits: accepted inputs are Google Merchant / Facebook catalog XML, CSV, TSV, or a Shopify store URL. That clarifies what feed_url actually accepts, useful for a free-form URL parameter.

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 concrete verb+resource (fetch a product feed and score AI shopping readiness 0-100) and immediately enumerates what the output contains (gaps, sample questions, thinnest products, fix link). An agent can distinguish this from get_feed_fix_guide and list_ai_shopping_platforms without opening a schema.

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?

Usage is implied by the described inputs and outputs, but there is no explicit when-to-use/when-not guidance and no named alternative. It references 'a link to fix the gaps' — which clearly relates to get_feed_fix_guide — yet never routes the agent to it, leaving the scan-then-fix handoff to inference.

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