Get short-lived download URL for a document

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

Annotations already indicate readOnly and idempotent. The description adds that it returns a redirect target (not the bytes), the URL is short-lived, and bytes are not proxied. This goes beyond annotations, though it could mention TTL or access scope.

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 with no redundancy. Each sentence adds value: first explains the endpoint and return type, second clarifies what is not done. Front-loaded with action verb 'Resolves'.

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 simple read-only tool with one parameter, annotations, and no output schema, the description covers the core behavior (what is returned, what is not proxied) sufficiently. No major gaps for an agent to misuse the tool.

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 0% and the description does not explain the parameter 'document_id' beyond hinting at its role in the URL path. It does not clarify expected format, required permissions, or that it is the Clio document ID. Minimal compensation for missing schema descriptions.

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 it resolves a specific endpoint ('GET /documents/{id}/download.json') and returns a redirect target (short-lived signed URL). This distinguishes it from sibling tools like clio_get_document, which likely returns metadata, and other generic tools.

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 for obtaining a download URL but does not explicitly state when to use this over alternatives like clio_api_request or clio_get_document. No exclusions or context about prerequisites (e.g., authentication, document access) are provided.

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