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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description usefully adds the scope of impact ('stops working for everyone who has it') and immediacy. It does not say whether the revocation is reversible, whether a new link can be issued, or which link is affected when projectId is omitted — a real gap given required parameters is 0.

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?

One sentence, front-loaded with the action and followed by the consequence; nothing is padded. It is efficient but leaves no room for the missing parameter and reversibility details.

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?

This is an irreversible destructive mutation with no output schema and an undocumented optional parameter, so the description carries a heavy burden. It covers the broad effect but omits what is destroyed at the link level, error behavior, and how to target the right link.

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 parameter projectId has 0% schema description coverage and is not mentioned in the description at all. Because it is optional rather than required, the agent has no way to know whether omitting it targets the project's only link or all links, so the description fails to compensate for the schema gap.

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 states a specific verb and resource ('Turn the review link off') and its effect ('stops working for everyone who has it'), which distinguishes it from create_share_link and get_share_link. Minor friction: the name says 'share link' while the description says 'review link', so an agent must infer these are the same object.

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?

Usage is only implied by the effect statement; there is no explicit when-to-use guidance, no note about prerequisites, and no reference to the sibling tools that create or read share links. An agent can infer the intent but gets no routing help.

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