clickup_task_replace_estimates

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

Discloses key behaviors: replaces full set, removes estimates for users not in array, body shape, and Business plan requirement. No annotations provided, so description carries full burden; it covers major behavioral aspects but omits error handling or idempotency.

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?

Three sentences, each earning its place: purpose, usage guidance with alternative, and body shape/requirements. No redundancy, front-loaded with key intent.

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 no annotations and no output schema, description covers purpose, alternative, and constraints. Lacks details on return value or success/error responses, but typical for a replacement tool.

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 coverage is 100%, and description adds value by explaining array behavior, highlighting 'at least one entry required', and referencing ClickUp's spec. Adds context beyond schema but could elaborate on assignee format (already in schema).

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 replaces the full set of per-user time estimates on a task, distinguishing it from setting a single estimate. It names the specific verb 'replace' and the resource 'task estimates'.

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 users to use clickup_task_set_estimate when only setting one estimate without disturbing others. Implicitly explains not to use if you want to keep estimates for users not in the array. Lacks explicit 'when not to use' but alternatives suffice.

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