clickup_attachment_upload

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it's a write operation ('Upload'), specifies the data format ('multipart/form-data'), indicates storage location ('ClickUp's CDN'), and mentions the return value ('Returns the created attachment object'). However, it lacks details on error conditions, rate limits, or authentication requirements.

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 efficiently structured in three sentences: first states the core purpose, second adds technical and behavioral context, third specifies the return value. Every sentence adds value with zero waste, making it appropriately sized and front-loaded.

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 mutation tool with no annotations and no output schema, the description does well by explaining the operation, data flow, storage, and return format. It could be more complete by mentioning potential errors or size limits (though size limits are noted in the schema), but overall it provides sufficient context for the agent to understand and use the tool effectively.

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 description coverage is 100%, so the input schema already fully documents both parameters. The description does not add any additional parameter semantics beyond what's in the schema descriptions (e.g., it doesn't explain file_path constraints beyond 'local file' or task_id format). Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('Upload a local file as an attachment') and the resource ('on a ClickUp task'), distinguishing it from sibling tools like clickup_attachment_list (which lists attachments) and clickup_task_create (which creates tasks). It specifies the exact operation with verb+resource+scope.

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 provides clear context for when to use this tool ('Upload a local file as an attachment on a ClickUp task') and mentions an alternative ('Use clickup_attachment_list to see attachments afterward'), but does not explicitly state when NOT to use it or compare it to other attachment-related tools beyond the listed sibling.

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