List Collections

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (IDs and names) and implies a harmless read, but says nothing about pagination limits, permission requirements, or whether all collections are always returned. Adequate for a trivial read, but with clear gaps it cannot fully compensate for the missing annotations.

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?

Front-loaded with the core purpose, then the disambiguation, then a usage hint. Slightly verbose and the trailing 'Returns: A list of collections with their IDs and names' partially duplicates the output schema, but every sentence is short and carries a clear signal.

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?

An output schema exists, so describing return values is not strictly necessary, though the description's restatement is harmless. For a zero-parameter listing tool with sibling disambiguation and a follow-up hint, the description is essentially complete; only edge-case behavior (empty collections, permissions) is unaddressed.

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 the baseline is 4. The description adds no parameter detail because there is none to add, and the only argument syntax mentioned (collection="name") belongs to the sibling list_boards, not this tool.

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?

States a specific verb+resource ('List all collections (folders) in the organization') and immediately disambiguates from the sibling list_boards by explaining that collections are folders containing boards. An agent can distinguish it from list_boards, list_organizations, and list_tags without opening any schema.

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?

Gives explicit when-to-use context ('If you're looking for a board but can't find it with list_boards, it may be inside a collection') and names the follow-up call with its argument form, list_boards(collection="name"). Nothing about routing between these two tools is left to inference.

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