clickup_goal_delete_kr

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It explicitly states the tool is 'destructive and irreversible,' explains that historical progress is lost, and that the goal's completion percentage is recalculated. This is beyond a simple 'delete' and adds valuable 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?

The description is two sentences, front-loaded with the primary action, and every sentence adds unique information: what it does, the consequences, and the return value. No extra words.

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 simple delete tool with one parameter and no output schema, the description covers the purpose, behavioral consequences, and return format. It is complete enough for an agent to invoke correctly.

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?

Input schema has one parameter (kr_id) with a description that already explains how to obtain the value. Schema coverage is 100%, so the description adds only marginal value by relating the parameter's consequences on the goal. Baseline 3 is appropriate.

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 'Permanently delete a single key result from a ClickUp goal' with a specific verb (delete) and resource (key result). It distinguishes from sibling tools like clickup_goal_delete (deletes entire goal) and clickup_goal_update_kr (updates key result).

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?

While the description implicitly indicates when to use the tool (when needing to delete a key result), it does not explicitly compare with alternatives or provide usage guidance such as when not to use it or prerequisites. No siblings are named for direct comparison.

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