list_collections

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does add useful context by listing the returned fields and the 'max 1000' limit. However, it does not explain what happens when more than 1000 collections exist, whether pagination is supported, or any access or read-only implications, leaving notable gaps.

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 a single, concise sentence with no filler. It front-loads the verb and resource, then lists the specific data returned and the limit. Every word earns its place.

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?

For a parameterless list operation with an output schema, the description covers the essential return contents and a key limitation. It is not overly verbose, though it could be slightly more complete by clarifying pagination or truncation behavior when the max is exceeded.

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, so the description does not need to explain parameter meaning. The '100%' schema coverage is trivial in this case, and the 0-param baseline of 4 applies. The description appropriately focuses on the output rather than inputs.

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 action ('Discover') and resource ('collection IDs, normalized names, descriptions and active counts'), and adds a specific limit ('max 1000'). However, it does not differentiate from the sibling 'discover_collections', which appears to serve a very similar purpose, so the clarity is strong but not fully distinguishing.

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 explicit guidance is given about when to use this tool versus alternatives such as 'discover_collections' or 'get_collection_history'. The description provides output contents but no context about prerequisites, search/filter behavior, or situations where another tool would be preferable.

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