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

The annotations declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so safety is partly covered. The phrase 'They show in a minute or two' adds genuine value by signalling asynchronous, eventually-consistent behaviour after the call. However, it never clarifies whether this triggers an external Google/G2 fetch, whether it creates review records, or what quota or rate limits apply to an open-world call.

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, front-loaded with the action and the source types, with no filler. The pronoun 'They' in the second sentence is slightly ambiguous, since it is unclear whether the reviews appear in the API response, in a widget, or in the dashboard.

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 one-parameter tool this is close to sufficient, but with no output schema the description should say what the call actually returns (reviews, a job status, or nothing) and how long to wait before re-reading. The asynchronous hint is present but not operationalised.

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?

There is only one parameter and schema coverage is 100%, with the schema itself pointing at list_review_sources for the id. The description adds nothing beyond that, which is acceptable at this coverage level but not enriching.

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 names a specific verb ('Gets the new reviews') and resource ('a Google or G2 source'), so the agent can tell what it fetches. It does not, however, distinguish itself from the nearby get_review_source or import_reviews siblings, leaving the sync-versus-read-versus-import boundary to inference.

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 statement about when to call this instead of get_review_source, list_review_sources, or import_reviews, nor any mention of prerequisites such as an already-connected account. The only implied guidance is that the source must exist, which is already in the schema.

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