list_collections

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

No annotations are supplied, so the description carries the full behavioral burden. 'List' implies a read, and the return fields are hinted at, but there is no statement about pagination, result volume, ordering, or required permissions for what is presumably a bulk-read operation.

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?

Two short sentences, front-loaded with the operation and result contents, with the usage note following. No filler or redundancy, though the second sentence is thin and could carry more routing value.

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 zero-parameter tool with no output schema, the description does supply the key return fields, which is the main thing needed. It stops short of pagination/ordering behavior and of differentiating this list from the run-status siblings, leaving the agent to guess in a crowded toolset.

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 takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description's mention of returned fields is a mild bonus rather than parameter semantics.

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?

Names a specific verb and resource ('List collections') and even enumerates the returned attributes (source URL, latest status, content counts), which is more than a tautology. However, it never distinguishes itself from siblings that also surface collection/run data, notably get_run_status and start_collection, so an agent cannot tell from the text alone which to pick.

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?

'Use for questions about existing collections or the latest run' gives an implied context for invocation, but offers no explicit when-not guidance and names no alternative tool. With siblings like get_run_status and get_failure covering adjacent run information, the absence of routing guidance is a real gap.

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