Download estimate PDF

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds meaningful behavioral context beyond annotations: the link is signed and expires after 30 seconds. This is critical for correct invocation, though it could have elaborated on what happens if the link expires.

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?

Two tightly written sentences with no wasted words. The purpose is front-loaded, and the critical expiry warning follows immediately. 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?

The description explains the return value (a download URL) and its key caveat (signed, 30-second expiry), which is sufficient for a read-only download tool with no output schema. The only minor gap is the lack of explicit guidance on the estimate_id parameter, but the name and tool context make it inferable.

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 67%, leaving estimate_id without documentation, and the tool description does not add parameter semantics. The parameter name is self-explanatory, but the description doesn't compensate for the missing schema coverage or explain how the estimate_id should be supplied.

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 specific verb and resource: 'Return a download URL for the estimate PDF.' This clearly identifies the tool's function and distinguishes it from sibling PDF-related tools like download_sales_invoice_pdf by specifying 'estimate PDF'.

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 description provides clear context on when to use the tool via 'use it immediately' and the expiry constraint, but does not explicitly contrast it with sibling download tools. It implies the scope (estimate PDFs) and the timing constraint, but lacks explicit exclusions or alternatives.

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