Download document to the work folder

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the side effect (a file is written to the work folder), the default location (default /root/Documents/Clio MCP, subfolder per matter), and the return value. It says nothing about overwrite behavior, file-size limits, permissions/auth needs, or what happens on a partial download, leaving notable gaps.

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 sentences, front-loaded with the core action and destination, and the second sentence handles intent and the follow-up tool. Slightly dense with path details, but no wasted sentences.

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 tool with no output schema, the description covers the key return value (the file path) and the intended workflow including the follow-up upload tool. Auth requirements and error/edge-case behavior are absent, but the essential information for correct invocation is present.

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 coverage is 67%, with target_dir and document_version_id already documented in the schema. The description adds the default behaviors (latest version, default work folder with subfolder per matter) which reinforces the schema, but the neglected document_id parameter has no schema description and the description doesn't explain it beyond 'a document'.

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 and resource ('Downloads a document (or a specific version) from Clio to the work folder on the PC') plus the destination and the returned value (the file path). It also clarifies scope ('or a specific version'), so an agent can immediately tell what operation this performs.

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?

It gives a clear purpose-driven context ('Intended for opening and editing the document with Claude') and routes the follow-up action to a named sibling ('upload the edited file back as a new version with clio_document_upload_version'). It does not, however, state when NOT to use it versus siblings like clio_document_read or clio_document_get, so exclusions are missing.

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