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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value by clarifying what the destruction means (the portal becomes unopenable), but omits whether the revocation is reversible, whether the link record is deleted or merely deactivated, and what authorization is needed.

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?

A single front-loaded sentence with zero filler; the effect is stated immediately after the action. It is efficient, though the extreme terseness leaves room that a destructive tool arguably needs.

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 destructive, open-world mutation with no output schema and 40% parameter coverage, the description is too thin: it does not identify the target id's meaning, explain the required idempotency_key, or address reversibility and permissions. It is not misleading, but it is not sufficient for confident invocation.

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?

Schema description coverage is only 40% and the description supplies no parameter information at all. It never clarifies which id is expected (the review link's UUID), why idempotency_key is required, or the role of brand_id, leaving low-coverage parameters undocumented in both schema and prose.

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?

Names a specific verb (revoke) and resource (client review link) and states the observable effect: the review portal can no longer be opened. An agent can distinguish it from create_client_review_link and list_client_review_links by the verb alone, though the description never explicitly names those siblings or the other revoke_* tools.

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 clause ('so its review portal can no longer be opened'), which suggests disabling access, but there is no explicit when-to-use, when-not-to-use, or alternative (e.g., revoke_connect_link vs revoke_report_link vs revoke_workspace_invitation). No prerequisites or permission requirements are stated.

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