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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful behavioral detail beyond annotations: it returns only the first 'limit' collections, reports total matches, and flags empty collections, helping an agent predict pagination and result scope.

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 sentences, front-loaded with the main output and audit purpose. The phrase 'potentially stale collections' is somewhat vague, but every sentence earns its place and there is no unnecessary repetition.

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 detailed parameter schema, output schema, and safety annotations, the description covers what the tool returns, pagination behavior, and intended audit use cases. The only minor gap is the undefined meaning of 'stale,' which is acceptable for a read-only audit 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 coverage is 100%, and the limit parameter is already documented thoroughly with default, cap, sorting, and total-match reporting. The description echoes the limit behavior but adds little new parameter meaning, so the baseline of 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 states a specific verb and resource: it audits collection membership by returning collections with product count and last-updated date, flagging empty collections. This clearly distinguishes it from sibling audit tools focused on products, pages, SEO, or inventory.

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 names concrete use cases: collection hygiene, empty collections, and potentially stale collections, giving an agent clear context for when to choose this tool. It does not explicitly name alternatives or when-not conditions, but the context is sufficient given the sibling tool names.

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