turbosign_download

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the key constraint that only completed documents can be downloaded, and that output_path must be an absolute path in an existing directory. While it doesn't detail error handling or side effects like file overwriting, it covers the most critical behavior for a download tool.

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, direct, and without fluff. It front-loads the purpose first, then adds constraints. Every sentence earns its place, making it highly efficient.

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 tool is simple with 2 required parameters and an output schema exists, so return values need not be explained. The description covers the essential purpose and constraints. It could mention behavior on invalid input or file conflicts, but for a basic download tool, it is adequately complete.

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 0%, so the description must compensate. It adds meaning to output_path by specifying it must be an absolute path in an existing directory, but does not elaborate on document_id. This partial compensation is insufficient to fully cover both parameters, hence a mid-range score.

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 tool's action: 'Download a completed signed document to a local file.' This specific verb+resource combination distinguishes it from sibling tools like turbosign_send or turbosign_status, making its purpose 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 provides a usage condition ('Only completed documents can be downloaded') and a path prerequisite, but does not explicitly mention alternatives or when to prefer this tool over others. Usage is implied by the tool name and context rather than explicitly contrasted with siblings.

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