clickup_upload_attachment

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

With no annotations, the description carries the full behavioral burden and does little beyond the action itself. It implies local filesystem access, but says nothing about size limits, required permissions, overwrite/duplicate behavior, or what happens on failure. Upload is a mutation, so the absence of any side-effect disclosure is a real gap.

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?

A single efficient sentence with the verb and target front-loaded and no filler. It is appropriately sized, though the ellipsis in the example list is slightly informal for a specification.

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 3-parameter tool with no output schema, the description covers the core action adequately. It is not complete though: with no annotations and no output schema, expected results and any upload constraints (size, permissions) are left entirely unstated.

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 task_id, filename, and file_path are already documented. The description adds only the 'local file' constraint, which the schema already implies via the absolute-path wording; 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 (upload) and resource (file as attachment to a task), with an illustrative parenthetical of file types. It clearly reads as distinct from sibling task/comment/checklist tools, though it never explicitly names what it is not.

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?

Usage is implied by the purpose – attaching a file to an existing task – and no sibling overlaps, so no alternative needs routing. However there is no explicit when-to-use, prerequisite (e.g. task must exist), or guidance on sources of the file.

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