clickup_attachment_upload

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

With no annotations, the description fully conveys behavioral traits: the file is read from disk, posted as multipart/form-data, stored on CDN, and returns the attachment object. It also notes size limits. This is above average for transparency.

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 three sentences, each adding essential information: purpose, mechanism, sibling reference, and return value. No unnecessary words; front-loaded with the key action.

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?

Given the tool's simplicity (2 params, no nested objects, no output schema), the description is complete. It covers operation, data flow, return format, and a link to the sibling tool. Minor gap: no error handling details.

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 input schema covers both parameters with descriptions, and the description adds value by explaining that the filename becomes the attachment title and that size limits apply. task_id's description guides to clickup_task_list for retrieval.

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 uploads a local file as an attachment to a ClickUp task. It includes technical details (multipart/form-data, CDN) and distinguishes from the sibling tool clickup_attachment_list by directing the user to use that for viewing.

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 specifies when to use the tool (to upload a file as an attachment) and mentions the alternative clickup_attachment_list for viewing. It could be improved by adding conditions like file size limits or prerequisites, but context is generally clear.

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