list_collections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the endpoint but no further behavioral details, such as whether results are paginated or if it returns all collections without filters. Since annotations cover the safety profile, a 3 is appropriate.

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, consisting of a single phrase and the endpoint path. Every word earns its place, and the main action is front-loaded. There is no redundancy or fluff.

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 simple read-only list operation with no parameters and an output schema present, the description is adequate. It conveys the action and the resource, and the annotations cover safety. It does not mention potential caveats like result limits, but given the simplicity of the tool, nothing critical is missing.

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 schema is trivially fully covered. There is no parameter information needed in the description, and the baseline for 0 params is 4. The description does not need to compensate for any missing parameter documentation.

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 'Get api collections' with the endpoint path, clearly indicating a read operation to retrieve collections. It is distinct from sibling tools like create_collections and delete_collections_by_id, and the name implies listing rather than fetching a single item (which would be get_collections_by_id). However, it does not explicitly say 'list all' or 'return all collections', leaving some nuance implicit.

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 provides no guidance on when to use this tool versus alternatives such as get_collections_by_id or list_libraries. It does not mention any prerequisites, filtering options, or scenarios where another tool would be more appropriate. The usage context is entirely left to inference from the tool name.

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