Delete Goal

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

Annotations already flag destructiveHint=true, and the description adds important behavioral context beyond those annotations: the action is irreversible ('cannot be undone') and returns a success message. This helps the agent understand the side effects and expected response without requiring additional inference.

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 consists of three short, purposeful sentences: the action, the irreversibility warning, and the return behavior. Every sentence adds distinct value and there is no redundant or extraneous wording.

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 one-parameter destructive tool, the description fully covers what the tool does, warns about permanence, and states the return value. It omits error conditions and permission requirements, but these are not essential for correctly selecting and invoking this straightforward deletion operation.

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 input schema has 100% coverage for the single required parameter goal_gid, including its type and example. The tool description itself does not add any additional parameter meaning, so it appropriately sits at the baseline for full schema coverage.

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 uses the specific verb 'delete' and identifies the resource 'goal,' clearly distinguishing it from sibling tools like asana_create_goal, asana_get_goal, and asana_update_goal. The additional warning 'This cannot be undone' reinforces its purpose as a permanent deletion action.

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 this tool (when you want to permanently remove a goal) but provides no explicit comparisons to alternatives or exclusions. It does not mention prerequisites, permissions, or when not to use it, leaving the agent to infer the usage context.

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