Add a price catalog item

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description does not need to restate that. It adds one genuinely useful data-model fact — that catalog is the sole store for pricing — but says nothing about duplicate-name handling, required permissions, or what is returned after creation.

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 action and resource before the usage trigger. The only mild redundancy is that 'with pricing' and 'the ONLY place to store pricing information' restate the same idea, costing a little space without adding new information.

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 6-parameter create tool with full schema coverage, annotations covering the safety profile, and no output schema to explain, the description supplies purpose and trigger condition. Nothing critical to correct invocation is missing, though duplicate-handling rules would have been a nice extra.

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%, and every property (cost, name, price, itemType, isTaxable, description) already carries its own description and example, including the enum semantics for itemType. The prose adds no field-level meaning beyond that, so the baseline 3 applies when the schema does all the work.

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 gives a specific verb and resource — 'Add a new service or product to the catalog with pricing' — so an agent immediately knows this creates catalog/pricing entries. It implicitly separates itself from line-item or estimate tools by declaring this is 'the ONLY place to store pricing information,' but it never names a sibling such as add_line_items, so the differentiation is indirect rather than explicit.

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?

'Use when user mentions pricing for services/products' gives a concrete trigger condition, and the 'ONLY place to store pricing' line frames it as the canonical path for pricing data. There is no when-not guidance, no mention of required prerequisites (e.g., an existing business/profile context), and no named alternative for cases where the user is pricing a one-off job line rather than the catalog.

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