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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description goes further with what an agent actually needs: nothing is purchased, reserved, or charged, a free PDF proof is emailed before printing, and constraints of minimum 25 sets and 1-150 titles apply. This is real side-effect disclosure beyond the annotation set.

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?

Front-loads the trigger and the return value, then packs constraints and exclusions into the remaining sentences with no filler. Dense but every clause carries routing or constraint information; only the parenthetical stacking makes it slightly heavy.

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?

There is no output schema, yet the description explains what comes back (exact price plus a pre-filled designer orderUrl) and the review/checkout flow. Combined with the exclusions and limits, an agent has everything needed to call this correctly and to know it commits nothing.

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% and the description's numeric limits (25 sets minimum, 1-150 titles) and the options-map hint duplicate what the schema already says. It adds no format or syntax detail beyond the structured fields, so the baseline 3 for fully-documented parameters is correct.

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 (draft) and resource (custom tab order) plus the concrete return artifacts: an exact price and an orderUrl that pre-fills Tabzoola's designer. This clearly separates it from quote_price (quotes for edge cases) and get_pricing_capabilities (option lookup), so an agent can route without opening a schema.

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?

Gives an explicit trigger ("when the user has their actual list of tab titles... and wants an order drafted") and explicit exclusions ("Do not use for reverse-printed tabs, PMS ink or custom sheet sizes (quote only)"), effectively routing those cases to the quote sibling. When-to-use, when-not-to-use, and the alternative are all present.

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