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

Annotations already declare readOnly, idempotent, non-destructive and openWorld. The description reinforces the safety profile ('Read only') and adds genuine behavioral context beyond the annotations: the tool diagnoses only, and remediation happens externally before Google rechecks. It does not describe pagination or rate behavior.

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 dense paragraph front-loads the returned fields before the parameter behavior, which is the right ordering. It is tight with no filler, though the run-on enumeration of issue fields 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?

There is no output schema, but the description enumerates the return shape (offer id, title, link, and per-issue severity, attribute, applicability, explanation), so an agent knows what comes back. Combined with parameter and workflow notes, it is nearly complete; only 'account' scoping is unaddressed.

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?

With 60% schema coverage, the description meaningfully compensates: it explains 'all' (include products without issues), 'issue' (filter to one issue code from merchant_issues), and 'search' (matches title or offer id). Only 'account' is left unexplained in both places, a minor gap.

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 precisely states the resource (Merchant Center products) and enumerates the returned fields (offer id, title, link, per-issue severity/attribute/scope/explanation), so an agent knows exactly what this tool surfaces. It also references the sibling merchant_issues as the source of issue codes, distinguishing itself from that tool.

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?

It clearly explains the default behavior ('by default only products with issues') and the effect of the issue and search parameters, plus the workflow ('fix the feed or the site, then Google rechecks'). It stops short of explicit when-not guidance or naming a direct alternative tool, so it is strong but not exhaustive.

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