Goals Delete Goal Event

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

Annotations already provide destructiveHint=true and readOnlyHint=false, clearly indicating a destructive operation. The description adds minimal value by stating it may 'delete, clear, reset, or otherwise remove data,' which is partially redundant and vague.

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?

Two sentences, front-loaded with the core action. The second sentence is vague but short. Overall efficient with no unnecessary verbosity.

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 operation with 4 parameters and no output schema, the description lacks detail on return behavior, side effects, or specifics of what 'delete, clear, reset' means in practice. The tool's purpose is clear but not fully contextualized.

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?

With 50% schema description coverage, the description does not add any parameter explanations. Required 'event_id' and optional 'session_path' lack context, and the description does not compensate for these gaps.

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 'Delete goal event,' clearly identifying the action and resource. However, the vague addition 'This may delete, clear, reset, or otherwise remove data' does not differentiate it from similar tools like goals_delete_goal or goals_update_goal_event.

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 on when to use this tool versus alternatives like goals_delete_goal or goals_update_goal_event. Context signals indicate sibling tools exist but description lacks any usage direction.

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