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

The description adds two useful facts beyond the annotations: the target collection is created if absent, and the call returns a product count. However, the annotations declare destructiveHint=true, and the description never warns that the existing `products` collection contents are overwritten by the sync — the highest-risk behavior for an agent to know. No contradiction, but a notable disclosure gap.

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?

Three short sentences, zero filler, with the core action front-loaded. The trigger condition and return value are appended in decreasing order of importance.

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 helpfully states the return value, and it covers what the tool does, when to run it, and its collection-creating side effect. The one gap is overwrite semantics on the target collection, which the destructive annotation flags but the description does not explain.

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% with a single, self-explanatory `siteId` parameter, so the schema carries the parameter burden. The description adds no format, default, or scoping detail for siteId, making this baseline 3.

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 ('Sync the site's Stripe catalog'), names the destination collection, and notes the side effect (creating it) and the return value. This separates it cleanly from read-only Stripe siblings like stripe_get_product, stripe_search_products, and stripe_list_categories.

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?

'Run after products change in Stripe' gives an explicit trigger condition, which is real usage guidance. It stops short of naming alternatives or exclusions (e.g. what to use instead if you only want to read the catalog), so it is clear context without full routing.

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