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

Goes well beyond the annotations: it discloses that replace=true overwrites existing reviews (matching destructiveHint=true), that the call is only proposed with status='confirmation_required', and that an action_id and plan_token must be confirmed via confirm_action before any write occurs. This is exactly the mutation/auth-flow context an agent needs.

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?

Front-loads the most important constraint (real reviews only), then replace semantics, then the confirmation protocol. The 'CONFIRMATION:' label makes the workflow scannable, though the sentence about action_id and plan_token is slightly dense.

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 write tool with no output schema, it covers the safety profile, the overwrite behavior, and the two-step confirmation handshake. Minor gaps remain around how the reviews block renders or what happens when no reviews block exists on the site.

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 coverage is only 33%, but the description compensates by explaining replace's destructive meaning and constraining the reviews payload to genuine client quotes. The website parameter is left to the schema, which does document it as an optional site id/name/subdomain.

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: add client reviews to the site's reviews block and display it. An agent can tell this apart from website_add_team or website_update_text by the target resource. It stops short of explicitly naming a sibling to use instead for other block types.

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?

Gives a strong content rule ('REAL client reviews the person gave (never invent any)') and clarifies the replace=true case, plus the propose→confirm flow. However it never says when to prefer this over a sibling like website_update_text or website_toggle_block, so routing is only implied by the resource name.

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