Get document download URL

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

No annotations are provided, so the description must fully disclose behavior. While it mentions 'short-lived presigned download URL,' it does not specify the URL's expiration duration, any requirements for document generation status, or authentication needs. The description is too sparse for a complete behavioral picture.

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 a single concise sentence, but it lacks important details while being short. It is not verbose, but the brevity comes at the cost of completeness. Acceptable but not exemplary.

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 tool with one parameter and no output schema or annotations, the description provides only the basic purpose. It does not cover edge cases (e.g., invalid documentId), error handling, or any constraints. Incomplete given the minimal supporting information.

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 schema has one required parameter (documentId) with no description (0% coverage). The tool description does not explain what documentId is, its format, or how to obtain it. This leaves the agent without necessary parameter context.

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 purpose: obtaining a short-lived presigned download URL for a single generated document. The verb 'get' and specific resource definition distinguish it from sibling tools like get_zip_url.

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?

No guidance on when to use this tool versus alternatives such as get_zip_url or build_zip. No mention of prerequisites (e.g., document must already exist) or context for invocation.

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