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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context beyond that: the price comes from the site's own engine, it assumes a single left-chest logo at a typical size, and exact pricing of real artwork happens on the product page. It doesn't say whether the returned price includes tiers, setup fees, or shipping.

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 tight sentences with the core promise front-loaded and the caveat second. Nothing is redundant, though the second sentence could more explicitly say 'this is an estimate' rather than leaving that to inference.

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 three-parameter, read-only pricing tool with no output schema, the description covers what is being priced and its fixed assumptions, which is the critical part. Gaps remain: no mention of the method parameter's price impact, no indication of what the response contains (unit price vs total), and no guidance on chaining from search_products.

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 67%, with slug and method documented and quantity undocumented. The description reinforces quantity ('at a quantity') but adds no tier, minimum, or volume-break semantics, and never mentions the PRINT/EMBROIDERY method choice despite it changing the price. Baseline 3 is appropriate since the schema already carries most parameter meaning.

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 states a specific verb+resource: it returns 'a real price from the site's own pricing engine' for one garment at a quantity. It also pins the exact configuration being priced (one logo, left chest, typical size), which is more precise than the title. It doesn't name siblings like get_product or start_order, so an agent must infer the boundary between quoting and ordering.

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?

'The product page prices the customer's real artwork exactly' implies this is an indicative figure rather than a binding price, which is useful usage context. However, it never explicitly says when to call this versus get_product or start_order, nor does it state prerequisites such as obtaining the slug from search_products (that only appears in the schema).

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