Goals Delete Goal

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

The description adds a vague 'This may delete, clear, reset, or otherwise remove data' clause that provides no concrete behavioral detail beyond the destructiveHint=true annotation. It does not disclose cascading effects, irreversibility, or what data is affected, which is critical for a destructive tool.

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 short and front-loaded with the primary statement 'Delete goal.' However, the second sentence is vague filler that does not earn its place, and the overall structure leaves room for more informative phrasing.

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 destructive tool with no output schema and only one documented parameter, the description is incomplete. It does not explain return behavior, side effects, or the relationship to archive_goal. An agent would be uncertain whether deleting a goal removes related events, linked accounts, or budget amounts.

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 documents fields and output_mode, but goal_id—the only required parameter—has no schema description and the tool description says nothing about it either. Schema coverage is only 67%, and the description does not compensate for the undocumented goal_id. No additional meaning is added beyond the 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 states a specific verb and resource ('Delete goal'), making its purpose clear. The name and title align, and the destructive nature is evident. However, it does not explicitly differentiate from the sibling goals_archive_goal, so it is not a 5.

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?

No guidance is given on when to use this tool versus alternatives. The sibling archive_goal/restore_goal tools likely offer non-destructive alternatives, but the description does not mention them or any prerequisites. The only implicit signal is the verb 'Delete', which leaves the agent to infer usage context.

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