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

Adds substantial non-obvious behavior beyond the annotations: asynchronous gathering, a possible {pending, task_id} first response, re-calling with the SAME task_id after ~1 minute, and credits charged only once. It does not explain why the annotations mark the tool destructive/non-idempotent, nor what 'refresh' does to credit consumption, so the disclosure is strong but not exhaustive.

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?

Dense, telegraphic prose that front-loads what the tool returns and the source/target pairing before the async caveat. Every sentence carries information; the style is terse rather than padded, though the fragment structure slightly taxes readability.

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?

An output schema exists, so return values need not be described, and the async workflow and billing model are covered well. But with 0% schema coverage on a 6-parameter tool, the undocumented refresh/language/location parameters leave real gaps an agent cannot resolve from any source.

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 0% across 6 parameters, so the description carries the full burden. It clarifies source (google/trustpilot), the source-dependent meaning of target, and task_id's polling role, but leaves refresh, language, and location entirely undocumented anywhere.

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+resource ('ratings + recent reviews for a business') and enumerates the two sources with their target formats ('google' = business name + city, 'trustpilot' = domain). It does not, however, explicitly distinguish itself from the closely-named sibling gbp_reviews, 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?

Gives a clear use case ('monitor your own or a competitor's reputation') and the add-on prerequisite ('SEO Intelligence add-on', 'Top up → Add-ons'). It stops short of naming when to prefer the sibling gbp_reviews over this tool, so alternative selection is left implicit.

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