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

Annotations declare idempotentHint and destructiveHint, and the description substantiates idempotency ('The link never changes once made') plus a real side-effect disclaimer ('sends nothing'). It also discloses the auth flow (sign-in prompt on printdash.io), which is genuinely non-obvious. It does not explain the destructive aspect — that publishing the quote exposes it to the recipient irrevocably — leaving that annotation unexplained.

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 sentences, front-loaded with the core action, then contrast, then prerequisites. Slightly dense with nested parentheticals, but each sentence carries distinct information (what it makes, what it doesn't do, what it requires).

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?

With an output schema present, return values need no explanation, and the description covers side effects, idempotency, and authentication. The main remaining gap is the unexplained destructive publication semantics, which matters for an agent deciding whether to expose a quote publicly.

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%, so both parameters are already documented, including the omit-to-inherit default for allow_payment. The description only restates 'pay online when allow_payment is on', adding no syntax or behavioral detail beyond the schema, so the baseline 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 ('Makes, or returns the existing, public link for a saved quote') and immediately scopes what the link is for. The parenthetical contrast with email_quote lets an agent distinguish it from the closest sibling without opening either 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?

Explicitly names the alternative ('It sends nothing (email_quote does)'), which resolves the most likely tool-selection ambiguity between sharing and sending. It lacks an explicit 'when not to use' for retrieval siblings like get_quote, so it falls short of a full when/when-not routing statement.

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