goals_delete

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

No annotations are provided, so the description carries the full burden. It only states the deletion, which is essentially redundant with the tool name, and fails to disclose whether the deletion is permanent, cascades to associated data, or requires specific permissions. This is a significant gap for a destructive operation.

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 a single, concise sentence that immediately states the action and resource. There is no fluff or repetition, and it is easy to parse.

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 the tool's simplicity (one parameter, no output schema), the description is minimally sufficient, but it lacks important context such as whether deletion is hard or reversible and what happens to associated key results or tasks. Without annotations, this makes it incomplete for an agent to fully assess the operation's impact.

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 has 100% description coverage for the required goal_id parameter, so a baseline of 3 is appropriate. The description's 'by ID' adds no new meaning beyond the schema's 'The ID of the goal to delete', but it does confirm the parameter's role.

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 'Delete a ClickUp goal by ID' uses a specific verb and resource, clearly distinguishing it from sibling tools like goals_get or goals_update. It also specifies the deletion mechanism (by ID), making the purpose unambiguous.

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 implies when to use the tool (when you want to delete a goal) but provides no explicit guidance on alternatives or exclusions. It does not mention that goals_update could be used for toggling status instead, nor does it state prerequisites like 'goal must not have associated key results'.

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