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

The description discloses data semantics (e.g., the count is dynamic, fromPriceAud is not a quote, and get_quote should be used for exact pricing) but does not address typical behavioral aspects such as read-only guarantees, potential side effects, rate limits, or auth requirements. With no annotations provided, the description carries the full burden, and it falls short on these points.

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?

The main action is front-loaded, but the description is verbose and somewhat repetitive, especially the price semantics ('The From price is not a quote' appears twice in different forms). While it is organized into two clear sections, the redundancy could be trimmed to improve conciseness without losing essential information.

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?

Given the absence of an output schema, the description provides substantial context by naming returned fields (names, types, discoveryKind, URLs, fromPriceAud, etc.) and clarifying their meanings. It also notes that the count is dynamic and points users to get_quote for exact pricing, which covers likely agent needs. Minor gaps include missing pagination or error handling details, but they are not critical for a listing endpoint.

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?

The tool has zero parameters and the schema already covers 100% of the input (an empty object). According to the rubric, a baseline of 4 is appropriate for 0 params, and the description offers no additional parameter-level meaning because no parameters exist to explain.

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 clearly states the tool's purpose: to list curated collection landing pages with specific fields (names, types, discoveryKind, URLs). It distinguishes itself from sibling tools like get_collection by explicitly focusing on listing multiple collections, and from get_categories by noting the curated, hand-picked nature. The action verb 'List' and the resource are unambiguous.

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 explains what the tool returns but provides no explicit guidance on when to use it versus alternatives such as get_collection, get_categories, or get_100_best. There is no mention of when not to use this tool or which specific scenarios it best serves, leaving the agent to infer use cases from the field list alone.

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