Meta catalog products

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description still adds real value by disclosing that the result is a bounded list and by enumerating the returned fields — significant because there is no output schema.

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 tight sentences with the resource and result shape front-loaded, followed by the follow-up-tool routing. No filler, though the field enumeration makes it slightly list-heavy.

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 compensates by naming the returned fields, and annotations carry the safety profile. Minor gaps remain: no statement of whether results paginate beyond the limit, and no mention of filtering options other than retailer_id.

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 coverage is 100%, with each parameter (limit, client_id, catalog_id, retailer_id) fully documented in the schema including defaults and fallback behavior. The description adds no parameter semantics beyond that; the field list it gives describes outputs, not inputs. 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+resource: a bounded list of products in the client's Meta catalog, and even enumerates the fields returned. 'Meta catalog' scopes it away from merchant_products, but the description never explicitly distinguishes it from that sibling by name.

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 forward-looking routing hint ('Use the product item id with meta_eco_plan_catalog_item_update'), which tells the agent what to do with results, but no guidance on when to choose this tool over merchant_products or meta_catalog_diagnostics, and no prerequisites or exclusions.

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