download_certificate

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

With no annotations provided, the description carries the full burden. It discloses that the tool downloads a PDF file to a local path and describes the certificate's content (audit trail with timestamps and IP addresses), which adds useful context. However, it doesn't mention potential behavioral aspects like error conditions (e.g., if the envelope isn't completed), file size limits, or authentication requirements.

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 description is two sentences with zero waste: the first sentence states the tool's purpose and key parameters, and the second adds valuable context about the certificate content. It's front-loaded and efficiently structured, with every sentence earning 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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and the nature of the output (PDF with audit details), but could improve by addressing error cases or prerequisites more explicitly. The lack of output schema means the description doesn't need to cover return values.

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 the schema already documents both parameters (envelope_id as UUID, output_path as local file path). The description adds no additional parameter semantics beyond what the schema provides, such as format details for the UUID or path constraints. This meets the baseline for high schema coverage.

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 clearly states the specific action ('Download') and resource ('audit certificate PDF for a completed envelope'), distinguishing it from sibling tools like download_archive or download_signed. It specifies the exact document type and its purpose, making the tool's function unambiguous.

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 implies usage by mentioning 'completed envelope,' suggesting it should only be used after an envelope is finished, but it doesn't explicitly state when not to use it or name alternatives. For example, it doesn't clarify if this tool is for audit certificates specifically versus other document types available in sibling tools.

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