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

Annotations already declare destructiveHint=true, so the safety profile is known; the description nonetheless adds real behavioral context beyond them by disclosing the cascade ('all its reviews') and the downstream effect on review widgets. It does not say whether deletion is permanent or reversible, which keeps it from a 5.

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?

Two short sentences with zero filler; the destructive scope is front-loaded and the consequence sentence follows immediately. Nothing could be cut without losing information.

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, single-parameter tool with no output schema, the description covers the resource, the cascade, and the widget impact, which is most of what an agent needs. The one meaningful omission is whether removal is permanent and whether widgets simply hide reviews or are otherwise altered.

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 the schema itself explains that source_id comes from list_review_sources, so the description needn't repeat it. With a single fully documented required parameter, 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 verb and resource ('Removes a review source') and immediately clarifies scope with 'and all its reviews', which distinguishes it from delete_review (single review) and other remove_* siblings. It stops short of naming an alternative tool outright, so a 5 isn't warranted.

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 explicit when-to-use guidance: nothing says when to remove a source versus updating it, disconnecting the account, or removing single reviews. The only usage-adjacent signal is the implied consequence for widgets, which an agent must infer rather than being told.

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