Revoke link credentials

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

Annotations only carry destructiveHint=true, but the description enriches the behavioral picture: 'keeping owner access intact', 'link stays protected', 'old share URL and secret stop working', and 'no new credentials are minted.' This clarifies the exact scope and permanent effect of the mutation.

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?

Three sentences with no filler: the first states the immediate action and its limits, the second states the outcome, and the third lists alternatives. The most important information is front-loaded.

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 mutation tool with no output schema, the description fully covers behavior, consequences, exclusions, and sibling alternatives. Nothing an agent needs to correctly select and invoke this tool is missing.

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 single label parameter is already fully documented in the input schema with 100% coverage. The description adds no new parameter-specific syntax, but none is needed; schema coverage carries the load, so baseline 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?

States a specific action: 'Immediately revoke the active secret code and capability token for a link' — identifying the verb, object, and effect. It also distinguishes itself from siblings by naming unprotect_link and renew_link as alternatives for different outcomes.

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 tells the agent when to use alternatives: 'To open the link to everyone instead, use unprotect_link; to mint fresh credentials, use renew_link.' This directly maps conditions to the correct sibling tool, leaving no ambiguity.

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