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

Annotations cover the write/no-destroy profile, and the description adds genuinely useful behavioral context beyond them: prices here are the ones quoted to customers, so the value must be formatted for display. It doesn't mention permissions or what happens on duplicate names, but the customer-facing price impact is a real, non-obvious trait.

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, front-loaded with the purpose, then the critical price caveat, then the pointer to list_catalog. No filler, though the price note slightly overlaps the schema.

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?

A 9-parameter creation tool with full schema descriptions, clear annotations, and no output schema — the description supplies the key semantic caveat (price is customer-facing) and a listing companion. Adequate for correct invocation.

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%, so every parameter is already documented. The description's price-format advice duplicates the price schema description almost verbatim, adding little beyond the structured data — 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 and resource ("Add a product or service to the catalogue") and clarifies the catalogue's role — it feeds answers to customers. It doesn't explicitly differentiate from the nearby create_store_product sibling, but the domain context makes the target clear.

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?

"See list_catalog for the current items" hints at checking existing entries first, which implies a de-duplication workflow, but there is no explicit when-to-use vs. when-not, and no guidance against the lookalike create_store_product sibling.

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