clickup_task_replace_estimates

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

With no annotations provided, the description carries full burden. It discloses that this is a PUT operation that 'replaces all user estimates', indicating a destructive mutation that overwrites existing data. However, it doesn't mention permission requirements, rate limits, whether changes are reversible, or what happens if the task has no existing estimates. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise with just one sentence plus a parenthetical clarification. Every word earns its place: 'Replace all time estimates for a task' states the core purpose, and '(PUT replaces all user estimates)' adds crucial behavioral context. No wasted words or redundancy.

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 is incomplete. It doesn't explain what the tool returns, error conditions, or important behavioral details like whether it affects multiple users' estimates. The 100% schema coverage helps with parameters, but overall context for safe and effective use is lacking.

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 the schema fully documents all 4 parameters. The description adds no parameter-specific information beyond what's in the schema. It mentions 'time estimates' generally but doesn't clarify parameter relationships or usage. Baseline 3 is appropriate when schema does all the parameter documentation work.

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 ('Replace all time estimates') and resource ('for a task'), with the parenthetical clarifying it's a PUT operation that replaces all user estimates. It distinguishes from sibling 'clickup_task_set_estimate' by emphasizing 'all' estimates rather than setting a single estimate. However, it doesn't explicitly contrast with that sibling tool.

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 no guidance on when to use this tool versus alternatives like 'clickup_task_set_estimate'. It mentions 'PUT replaces all user estimates' which hints at behavior but doesn't give usage context, prerequisites, or exclusions. No explicit when/when-not instructions are present.

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