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

Annotations already declare this is a non-readOnly, non-destructive, non-open-world write, so the safety profile is covered. The description adds the meaningful constraint that the target source must be a manual source, but says nothing about duplicate handling, whether the review is published immediately, or what happens if source_id points at a non-manual source.

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 no filler, and the key constraint (manual source) is included rather than buried. It borders on terse for a 13-parameter mutation tool, but nothing is wasted.

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?

The rich schema and existing annotations mean the agent can construct a call correctly from structured data alone. However, for a 13-parameter write operation with no output schema, the description leaves open what is returned and how duplicates or invalid source types are handled.

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%, with all 13 parameters individually documented including formats, bounds, and the platform enum, so the schema carries the parameter burden. The description adds no field-level meaning (e.g., which fields are ignored for certain platforms), so baseline 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?

"Adds a review by hand (a testimonial) to a manual source" gives a specific verb (adds) and resource (review/testimonial) plus a scoping constraint (manual source) that distinguishes it from the bulk/automated siblings like import_reviews and sync_review_source. It stops short of naming those siblings, so an agent must infer the boundary.

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?

"By hand" and "manual source" imply the usage context (single, manually entered testimonial rather than an imported or synced batch), which is real guidance but only implied. There is no explicit when-to-use/when-not statement naming import_reviews or approve_pending_reviews as alternatives.

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