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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond restating deletion: it doesn't say the action is irreversible, whether the review can be recovered, or what happens to aggregates/stats tied to the review. For a destructive tool, that is a meaningful missed opportunity even with annotations present.

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 short sentence with no padding, front-loaded with the verb, which is good. The brevity here reflects under-specification rather than disciplined conciseness, so it earns no more than an adequate score.

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 a destructive, single-parameter tool with no output schema, so the description carries the burden of warning about irreversibility and side effects. It says nothing about consequences, permissions, or post-deletion state, leaving an agent without the context needed to call it safely.

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 100%, and review_id is already documented as 'the id in get_review_source'. The description provides no additional meaning about the identifier, so the baseline of 3 applies.

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 gives a specific verb and resource ('Deletes a review'), which is understandable on its own. However, the qualifier 'of a manual source' is ambiguous: it isn't clear whether reviews from non-manual sources can also be deleted, or what 'manual source' means in this domain. It does not name any sibling (e.g. update_review, remove_review_source) to differentiate itself.

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?

There is no statement of when to use this tool rather than update_review (to modify) or remove_review_source (to detach a source). No preconditions such as ownership, review state, or approval status are mentioned, so the agent must infer the call conditions entirely from surrounding tools.

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