Merchant.Products.List

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about pagination behavior, default page size, auth/permission requirements, or whether the listing is truncated. Only the read-only nature is weakly implied by 'List'.

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 front-loaded sentence with zero filler. It is appropriately sized, though that size reflects thin content rather than disciplined editing.

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 annotations, a 0%-documented parameter, and a list operation that almost certainly paginates, the description leaves key call-shaping details unstated. The existing output schema covers return values, but invocation details (ID format, pagination, limits) are missing.

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% for the single required parameter, and the description only vaguely implies merchant_id is the account identifier. It gives no format guidance (bare numeric ID vs. 'accounts/123') or whether sub-account filters exist, so it does not compensate for the coverage 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?

States a specific verb and resource ('List products') scoped to a Merchant Center account, which is clear and unambiguous. However, it does not distinguish itself from nearby siblings such as merchant.product.get or merchant.product_statuses.list, so an agent must infer the boundary from names alone.

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?

No guidance on when to use this versus merchant.product.get or merchant.product_statuses.list, and no mention of pagination, filtering, or result limits. The agent is left to infer everything about invocation context from the tool name.

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