clickup_download_document_page_attachment

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

With no annotations, the description carries the full burden and does so: it discloses that the URL is short-lived (~5 minutes), potentially single-use on private-attachment workspaces, and must be fetched immediately and exactly once. This is precisely the operational constraint an agent would otherwise violate.

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?

Front-loaded with the action and the URL hazard, followed by the failure-recovery instruction. Every sentence carries distinct operational information with no restatement of the name or schema.

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?

A download tool with no output schema still gets its return described (short-lived download URL plus attachment metadata), plus the expiry/single-use semantics and the retry policy. Nothing an agent needs to call it correctly is missing.

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 100%, so all three parameters are already documented in the schema, including the page_id URL hint and the attachment_id provenance. The description adds no syntax or format detail beyond that, so baseline 3 applies.

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 (download a ClickUp doc page attachment) and names the sibling that produces the required attachment ID, so the agent can place it in the workflow without opening schemas.

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?

Explicitly directs the agent to get attachment IDs from clickup_list_document_page_attachments and states the recovery path if the URL expires ('call this tool again for a fresh URL'). The 'when-not' behavior (do not preview, HEAD-request, retry, or store) is spelled out.

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