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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. Beyond that, the description usefully discloses that the response shape branches on source type and that an "open" flag reports whether the owner enabled the form, which is real behavioral context. It stops short of saying whether a Google source still returns a QR image or what happens when the form is off.

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?

Three short sentences, front-loaded with what the result is and then the per-source variations. The phrasing is slightly telegraphic ("A 'Your reviews' source gives its testimonial form") and drops the implicit verb, but no sentence is filler.

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?

With no output schema and only one parameter, the description carries most of the load and does explain the main return components: link, QR image, form, open flag, and Google's review page. Missing are pagination-style details (none needed) and the edge case of a disabled form or absent QR code, but the agent has enough to call it correctly.

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 100% for the single source_id parameter, so the baseline is 3. The description adds meaning by indicating that the source's type changes the result, which helps an agent predict output, but it does not describe source_id itself or its format beyond what the schema says.

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 identifies the specific resource returned: the review-request link plus its QR code image, and it distinguishes the payload by source type ("Your reviews" testimonial form vs Google's review-writing page). It never uses an explicit verb like "retrieve," but the resource is unambiguous enough to separate it from siblings such as get_embed_code or get_upgrade_link.

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 when-to-use statement and no comparison to alternatives. The description explains what the output looks like per source type but never says to call this when you need a shareable review link, nor does it exclude anything. The only pointer is in the schema, which references list_review_sources.

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