clickup_field_set

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

With no annotations provided, the description carries full burden and does well: it discloses that this is a mutation operation ('Set or overwrite'), specifies the return value ('Returns an empty object on success'), and mentions the need to check field types first. It doesn't cover permissions or error handling, but provides solid behavioral context.

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?

Four sentences, each earning its place: purpose statement, value format guidance, sibling tool references, and return value. Front-loaded with the core action, zero wasted words, perfectly structured for clarity.

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: covers purpose, usage, parameters, and return value. It could mention authentication requirements or error cases, but given the schema coverage and sibling references, it's largely complete for agent use.

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 baseline is 3. The description adds significant value beyond the schema: it explains the JSON shape requirements for the value parameter with concrete examples for different field types, and references clickup_field_list for type information. This enhances understanding of parameter usage.

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 specific action ('Set or overwrite a single custom field value'), the resource ('on a ClickUp task'), and distinguishes it from siblings like clickup_field_list and clickup_field_unset. It's precise about what the tool does.

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 states when to use this tool ('Set or overwrite a single custom field value'), when to use alternatives ('Use clickup_field_list first to see the field type and option ids. Use clickup_field_unset to clear a value'), and provides clear prerequisites. This gives comprehensive guidance.

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