list_collections

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

With no annotations, the description alone must convey behavioral traits. It only says 'retrieve' without detailing pagination, filtering via the req parameter, authentication needs, or side effects. The tool's behavior is essentially opaque.

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 description is extremely concise at two words, but it sacrifices necessary detail. It is not verbose, but it is under-specified for a tool with a complex input schema and many siblings.

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 tool's complexity (nested parameter, many siblings, output schema), the description provides almost no context about what 'collections' are covered (e.g., all, top-level, subcollections) or how to use the query capabilities. The output schema may help, but the description still lacks completeness.

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 0% (the sole parameter 'req' lacks a description in the input schema). The tool description adds no parameter context, failing to compensate for this gap despite the complex nested object with multiple subfields.

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 'Retrieve collections' clearly indicates the action and object. However, it does not differentiate from sibling tools like get_collection (single) or list_collections_top (top-level only), leaving ambiguity about scope.

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 guidance is provided on when to use this tool versus alternatives. There is no context about prerequisites, appropriate scenarios, or exclusions, which is needed given many collection-related siblings.

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