Merchant Center report query

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond them by disclosing that it hits Merchant API reports:search and that it returns Google's raw result rows rather than a normalized/transformed shape.

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 API surface, followed by the return shape. No filler; slightly more compact than most peers.

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, the description correctly compensates by noting the return is Google's raw result rows, and the single input parameter is fully specified in the schema. An agent has enough to call it correctly, though pagination/result-size behavior is unstated.

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% and the single parameter is fully documented in the schema (MCQL statement, available tables, product_view id requirement, performance metrics). The description only restates "with an MCQL query" and adds no syntax, default, or format detail beyond the schema, so the 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?

States a specific verb and resource ("Run a Merchant Center report") and names the underlying API call (reports:search) plus concrete use cases (product status, free-listing performance). It is distinguishable from the GA4/GSC siblings, though it does not explicitly separate itself from merchant_product_issues, which covers overlapping product-status territory.

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?

The description implies when to use it by giving two example report categories, which is useful context, but it offers no exclusions or alternatives — it never says when to reach for merchant_product_issues or merchant_data_sources instead. Usage is inferable but not explicit.

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