download_envelope_document

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does add useful context by stating the return format ('Dictionary with document content (base64-encoded) and metadata'), but it does not explicitly confirm that this is a read-only operation or describe error handling, permissions, or side effects. The 'Download' verb implies safety but lacks full transparency.

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 extremely concise, with a single purpose sentence and clearly labeled Args/Returns sections. Every sentence is informative, and there is no redundant or extraneous content.

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 simplicity (two required string params, no nested objects, and an output schema), the description covers the essential aspects: purpose, parameter roles, and return format. It is complete enough for a straightforward download, though it could mention potential pitfalls like large files or non-existent documents.

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?

The input schema has 0% description coverage, so the description compensates by defining each parameter: 'envelope_id: The envelope ID' and 'document_id: The document ID to download.' This adds clear meaning beyond the bare schema, though the definitions are simple and could be more detailed (e.g., expected format).

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 opens with 'Download a specific document from an envelope,' which clearly states the action (download) and the resource (a specific document within an envelope). This verb+resource structure distinguishes it from sibling tools like list_envelope_documents, which lists documents rather than downloading content.

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 when you have a specific envelope_id and document_id, but it does not explicitly state when to use this tool over alternatives like list_envelope_documents. No mention of prerequisite steps or exclusions is provided, so the guidance is only implicit.

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