Generate estimate PDF

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds value by disclosing the 'regenerate' idempotent-ish behavior and the URL return value, which is meaningful given there is no output schema. It does not say whether the PDF is persisted or overwritten, whether generation is synchronous, or what permissions/state the estimate must be in.

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?

One short sentence with the action and result front-loaded and zero wasted wording. It is efficient, though borderline terse for a tool that mutates state (creates a PDF artifact).

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 tool with full schema coverage and no output schema, naming the returned URL is the key missing piece and it is present. However, prerequisites and side effects of PDF generation are not addressed, leaving gaps for an agent deciding when the call will succeed.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents estimateId. The description adds no syntax, format, or example for the ID, 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 ('Generate (or regenerate)') and a specific resource ('the estimate PDF'), and adds the useful detail that a URL is returned. It is clearly distinct from siblings such as wave_get_estimate or wave_send_estimate, though it does not explicitly name a boundary against any of them.

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 parenthetical '(or regenerate)' implies usage: call it when a PDF is needed for an existing estimate, including when one already exists. There is no explicit when-not guidance, no prerequisites (e.g., estimate must exist and be non-deleted), and no alternatives are named.

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