list_allocations

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds valuable context: it's an 'admin action' (implying elevated permissions), specifies authentication requirements ('Requires Application API key'), and mentions pagination behavior through the parameters. No contradiction with 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?

Extremely concise and well-structured - three sentences that each serve a distinct purpose: what the tool does, how to use it, and authentication requirements. No wasted words, front-loaded with the core functionality.

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 read-only listing tool with good annotations and full schema coverage, the description provides excellent context about permissions, prerequisites, and relationship to other tools. The main gap is lack of output schema, but the description partially compensates by specifying what information is shown. Could benefit from more detail about return format.

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 the schema already fully documents all parameters. The description adds minimal value beyond the schema - it mentions the node_id parameter context ('from list_nodes') but doesn't provide additional semantic information about the parameters beyond what's in the schema descriptions.

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 resource 'port allocations for a node', specifies it's an 'admin action', and distinguishes it from sibling tools by mentioning it requires node_id from list_nodes. It provides specific details about what information is shown (IP, port, alias, server usage).

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?

Explicitly states when to use ('Use list_nodes to find the node_id first') and provides prerequisites ('Requires Application API key'). It distinguishes from create_allocation and delete_allocation by being a read-only listing operation, and from other list_* tools by specifying it's for port allocations on a specific node.

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