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

Annotations declare readOnly=false, openWorld=true, destructive=false; the description adds real value beyond that by disclosing the external side effect (sending to the client portal), the per-call confirmation default, and the required API key scope. It does not cover reversibility or failure behavior, keeping it below a 5.

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?

The opening and second sentences restate the same idea ('Itemized estimate on the client card' appears twice), and the confirmation point is repeated, so the text is somewhat redundant. It is still readable and front-loaded, but not every sentence earns its place.

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 mutation tool with openWorld behavior and no output schema, the description covers the key agent concerns: what is created, the send/save distinction, confirmation requirements, and auth scope. Return-value details are not strictly needed since none are defined.

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%, so all four parameters are already documented, and the description's send explanation largely mirrors the schema's 'Send it to the client now. Default: false.' Baseline 3 applies since the schema does the heavy lifting.

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 precise verb+resource ('Creates an itemized estimate on the client card') and clarifies the two modes of operation, so an agent understands exactly what the tool produces. It does not name or contrast with sibling estimate tools, so it stops short of a 5.

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?

It gives clear conditional guidance: send=false saves only, send=true dispatches to the client portal for approval, plus a note about per-call confirmation. It does not route the agent between this and alternatives like thryv_create_invoice or thryv_send_message, so no explicit when-not guidance.

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