Merchant Center products

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the trailing 'Read only' adds little. What does add value is the pagination behavior (next_page_token for the next page), the 'processed view' framing, and the note that the returned id is the exact key merchant_plan_product_patch consumes. No auth or rate-limit context is given, but the safety profile is fully covered by annotations.

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 that front-loads the tool's identity and the page contents before the pagination note. Nearly every clause earns its place, though the enumeration of returned fields is lengthy and could be trimmed since some of it is discoverable at call time.

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 usefully enumerates the returned fields and explains pagination, and the schema covers client/account scoping. What is missing is any guidance on the read-to-patch workflow with merchant_plan_product_patch and when this listing should be preferred over the other Merchant Center siblings.

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%, so limit, client_id, account_id and page_token are already fully documented, including the next_page_token/empty-first-page semantics. The description restates the pagination rule for page_token and mixes in output-field detail (the composite id) rather than adding new parameter meaning, so baseline 3 is correct.

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 ('One page of the client's Merchant Center products') and enumerates exactly what each returned record contains (full product id, title, link, availability, price, data source, item issues, per-destination status). The composite id format contentLanguage~feedLabel~offerId makes it clearly distinguishable from sibling list tools like merchant_product_issues or meta_catalog_products.

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 one concrete usage instruction ('Pass next_page_token for the next page') and cross-references merchant_plan_product_patch as the consumer of the returned id, which implies the read-plan-patch workflow. However, it never says when to choose this over merchant_report_query, merchant_product_issues, or merchant_data_sources, so the routing guidance is only implied.

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