forward_close

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

Annotations already declare idempotent and non-read-only behavior. The description adds valuable context beyond those: best-effort execution and the specific error condition for unknown tunnel 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?

Two concise sentences, front-loaded with the main action, and no unnecessary wording. The structure is clean 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?

For a simple idempotent close operation with an output schema, the description covers the essential behavior and error semantics. It does not mention how to obtain valid tunnel ids, but sibling forward_list implies that source.

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?

With 0% schema description coverage, the description compensates by tying the 'forward' parameter to the tunnel id ('by id'). It does not detail the id format, but the single parameter's purpose is clear from the description.

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?

Clearly states the action 'Close a forward tunnel by id' with the specific ssh -O cancel reference. The verb and resource are precise, and it is readily distinguished from siblings like forward_open and forward_list.

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?

Provides useful context: closiing is by id, best-effort, and unknown tunnel ids cause errors. However, it does not explicitly mention when to use this tool versus alternatives, leaving that to be inferred from sibling tool names.

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