coronium_cancel_pool_key

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without any side effects, destruction semantics, or authorization requirements. It does not indicate whether cancellation is irreversible or what happens to associated proxies or sessions, which is a significant gap for a mutation tool.

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 highly concise, consisting of a single, clear sentence that is easy to parse and front-loaded with the key action. It contains no filler or redundant phrasing, though it is minimal to the point of lacking contextual detail.

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 simple mutation tool with one parameter and no output schema, the description is functionally minimal but misses important contextual details like prerequisites, irreversible effects, and what a successful response looks like. Given the lack of annotations, the agent is left with insufficient information to anticipate the tool's impact.

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 input schema provides complete coverage for the single 'id' parameter with a clear description ('Pool key id'). The tool description adds no additional semantic meaning beyond the schema, so the pre-specified baseline of 3 is appropriate.

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 action (cancel) and the specific resource (pool key), which distinguishes it from other cancel operations like cancel_modem. However, it lacks a brief explanation of what canceling a pool key entails, which could be ambiguous for users unfamiliar with the domain.

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 provides no guidance on when to use this tool versus alternatives such as topup_pool_key or list_pool_keys. It does not mention prerequisites, restrictions, or scenarios where this tool should be avoided, leaving the agent without decision criteria.

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