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

Discloses it is a write operation ('WRITES') and that it upserts, which implies idempotency. Annotations only provide destructiveHint=true; description adds that it affects future tax calculations. No contradictions.

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 sentences, front-loaded with action and consequence. No fluff.

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?

No output schema, and description does not mention return value or response structure. For a creation tool, this is a gap. However, parameter descriptions are comprehensive.

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 covers all parameters with descriptions. Description adds that the product_category is from Numeral's taxonomy and that upsert behavior uses reference_product_id as key, adding value beyond schema.

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?

Clearly states it creates or upserts a product with its tax category, referencing the API endpoint. Distinguishes from sibling tools which deal with other entities (customers, refunds, transactions) and product retrieval.

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?

Description implies use when adding a product to the catalog to drive tax calculations. No explicit exclusions or comparisons to alternatives, but context makes usage obvious given distinct sibling tools.

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