list-api-collections

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

No annotations provided, so description carries full burden. It only mentions pagination, but lacks details on authentication, rate limits, or behavior when no results. Does not disclose what happens with 'include' and 'extractFields' in terms of performance or response structure.

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?

Description is extremely concise, front-loading key information. However, it could include a sentence about common use cases without becoming verbose.

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 7 parameters (none required) and no output schema, description is incomplete. It does not explain the response format, pagination behavior (cursor vs offset), or how 'fields' and 'extractFields' interact. User may need to infer from parameter descriptions alone.

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%, so baseline is 3. Description adds no meaning beyond what schema already provides; 'with pagination' is already implied by 'before' and 'after' parameters. No clarification of complex fields like 'extractFields'.

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?

Description clearly states the action (list) and resource (API collections), and includes version information (OM 1.12+) and key feature (pagination). It distinguishes from siblings like 'list-api-endpoints' and 'get-api-collection-by-name'.

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 guidance on when to use this tool versus alternatives (e.g., searching, getting a single collection). No mention of prerequisites or context for pagination parameters.

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