tunnel_destroy

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

With no annotations, the description discloses key traits: immediate removal regardless of remaining reads/TTL, in-memory mutation, and return values including error for unknown or already destroyed IDs.

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 very concise with three front-loaded sentences that convey the action, usage, and behavior without extraneous words.

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?

The description covers purpose, usage, behavior, and return values. It does not mention how to obtain the tunnel ID, but that is a minor gap given the one-parameter simplicity.

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 schema already describes the 'id' parameter with a suitable description. The tool description adds no extra semantics beyond what the schema provides, so it meets the baseline for 100% coverage.

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 tool immediately removes a tunnel from memory, specifying the resource and verb. It distinguishes from sibling tools like tunnel_read and tunnel_create by noting the cancellation use case and preferring normal cleanup via maxReads/TTL.

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 explicitly advises when to use the tool (cancel before delivery, e.g., wrong recipient) and when to avoid it (let maxReads/TTL handle normal flows), providing clear context for selection.

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