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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered and the description need not restate it. The description adds only a loose sketch of the returned categories (checks, sources, trends) and no pagination, filtering, or auth context.

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?

A single short, front-loaded sentence with no filler. It is arguably too terse for the ambiguity of "Shelf Pass," but nothing is wasted.

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 should describe the return shape more concretely; "checks, sources and content trends" hints at it but does not specify structure. Annotations cover the safety profile and the free-form query param is schema-documented, so the remaining gap is moderate rather than severe.

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 100% and the single "query" object is self-documented as free-form key/value pairs, so the schema carries the weight. The description says nothing about query syntax or which keys are accepted, which is the baseline 3 for high-coverage schemas.

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 ("List") and resource (Shelf Pass checks, sources, content trends), so the agent knows it enumerates catalogue content. It distinguishes itself from siblings only by the "Shelf Pass" domain prefix, and the domain itself is undefined jargon, but the verb+resource pairing is clear.

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?

No when-to-use guidance and no mention of alternatives. The agent is left to infer that this is the discovery step before shelf_check, and nothing says when this tool should be preferred over the many sibling *_catalogue tools.

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