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

Goes well beyond the annotations: it discloses the authentication requirement and the fallback behavior (the connection prompts sign-in on printdash.io), that the original is unchanged, and that every line is re-priced at today's rates — a material side effect for a non-readOnly tool with destructiveHint=false. It stops short of spelling out that a second call yields a second independent quote (idempotentHint=false), which is the one behavioral consequence an agent could still get wrong.

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 tight sentences, each doing distinct work: what is created, what is not carried over / what happens to the original, and the auth prerequisite. Front-loaded with the core action with no preamble.

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 one-parameter copy operation with an output schema (so return shape needs no explanation) and full annotation coverage, the description supplies everything an agent needs: the identity of the new object, the re-pricing consequence, the artwork exclusion, and the sign-in requirement.

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 the schema already explains the single parameter accepts a quote number or the id from its link. The description adds nothing about the identifier beyond what the schema provides, so the baseline of 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 (saves a copy of a quote as a new quote) and immediately pins down the scope: new quote number, lines re-priced today, artwork excluded, original untouched. This clearly separates it from create_quote (build new), update_quote (mutate existing), and get_quote (read).

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?

Clear context for when this applies — copying an existing quote rather than authoring or editing one — plus an explicit exclusion (artwork is not copied). It does not name a sibling alternative or state when *not* to use it (e.g. use create_quote for a fresh job), so it falls short of a 5.

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