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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that output is explanatory and backed by 'evidence the merchant already owns', which is useful color, but says nothing about response size, pagination, or whether the full checklist is large.

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?

Roughly two sentences, front-loaded with the core purpose, and the calling convention is placed last as an actionable trailer. 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 a single optional parameter, annotations covering the safety profile, and no output schema, the description supplies enough to call it correctly and sets expectations about the nature of the return. It could add a word on output volume or format, which keeps it from a 5.

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% and the schema already documents issue_key with concrete examples (no_specs, thin_desc, llm_unanswerable). The description only restates the omit-for-all behavior, so the baseline 3 is appropriate.

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 verb (explain) and resource (a gap from scan_product_feed and its fix), and explicitly ties the tool to the sibling that produces the input. An agent can tell it apart from scan_product_feed 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?

It states the calling convention clearly ('Call with no argument to get the full checklist') and implies the input comes from scan_product_feed, giving a usable when-to-use context. It stops short of an explicit when-not-to-use or a named alternative, so it lands just under full marks.

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