Update product catalog

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the update replaces or merges catalog fields, what permissions are needed, or whether the change is reversible — all meaningful for a mutation on a nested object.

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?

It is a single short sentence, so there is no bloat, but the sentence is a tautology that could be deleted without losing information. Per the calibration, under-specification is not conciseness.

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?

For a mutation tool operating on a nested object with no output schema and half its parameters undocumented, a one-line tautology is completely inadequate. An agent has no way to construct a correct update payload from this definition.

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 only 50%: catalog_id has no description at all, and the data object's description ('Sent as {"data": {...}}. Fields: name, event_sources [pixel IDs].') is already in the schema, not the tool description. The description does not compensate for the undocumented catalog_id or clarify field-level update semantics.

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 restates the title and tool name almost verbatim: 'Update a product catalog.' It gives a verb and resource but no scope, no fields affected, and no differentiation from siblings like reddit_ads_create_catalog, reddit_ads_delete_catalog, or reddit_ads_update_product_feed.

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?

There is no statement of when to use this tool versus the other catalog tools. The agent must infer from the name alone that this modifies an existing catalog, and no prerequisites, exclusions, or alternatives are named.

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