list_collections

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention that the operation is read-only, that results are paginated (implicit in the schema but not stated), or any ordering or rate limits. The phrase 'List all' is misleading because pagination means a single call does not return truly all items.

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 two sentences: the first clearly states the action and scope, the second provides necessary context about what collections are. No redundant words or filler. It is front-loaded and efficient.

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 low complexity and lack of annotations/output schema, the description should compensate. It does not explain that responses are paginated or how to handle pagination to retrieve all collections. The agent might assume a single response suffices, leading to incomplete data retrieval.

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 100% (page and per_page both have descriptions), so the baseline is 3. The description adds no additional meaning beyond the schema. It could have explained that page controls which page of results and per_page limits items per request, but that is already in the schema.

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 verb 'List' and the resource 'all Intercom Help Center collections', immediately identifying the tool's purpose. It also explains what collections are ('top-level categories that contain sections and articles'), distinguishing it from sibling tools like list_articles or create_collection.

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 implies the tool is for listing collections but provides no explicit guidance on when to use it versus alternatives like get_collection (single item) or create_collection. It lacks when-not-to-use instructions or context about filtering, sorting, or pagination.

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