tenki_unbind_preview_url

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

The annotations already declare destructiveHint=true, and the description adds that the unbinding is from the current session/port, which clarifies what is affected. It does not go further to describe reversibility, whether the URL remains valid, or side effects on the session, but the annotation coverage lowers the burden.

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 a single sentence with no filler. It front-loads the action and object, and the parenthetical '(advanced routing)' adds useful context without bloat.

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 single-parameter tool with annotations covering destructiveness, the description is nearly complete: it states the action, target, and context. It could be more complete by clarifying what happens to the preview URL after unbinding, but the core information needed to invoke it correctly is present.

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 fully documents preview_url_id with a description, so parameter semantics are already covered. The tool description adds only the 'named preview URL' framing, which is marginal extra meaning beyond the schema.

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 uses a specific verb ('Unbind') with a specific resource ('named preview URL') and target ('current session/port'), making the operation concrete. It also clearly distinguishes this from sibling tools like tenki_bind_preview_url and tenki_delete_preview_url.

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 phrase 'Unbind a named preview URL from its current session/port' gives clear context for when this tool is appropriate, and '(advanced routing)' signals it is a specialized operation. However, it does not explicitly name alternatives or state when not to use it, such as when the URL should be deleted entirely.

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