wealthbox.events.delete

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

With no annotations, the description carries the full burden of behavioral disclosure, but "Delete event" only implies a destructive action. It does not disclose reversibility, side effects, permission requirements, or consequences for associated data, leaving the agent without critical safety information.

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 but under-specified. Concision should distill necessary information, not omit it. A single tautological sentence is not effective structure for a delete operation.

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 delete operation with no annotations, no output schema, and a single undocumented parameter, the description is completely inadequate. An agent cannot infer behavior, safety, expected return values, or error conditions.

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 one parameter 'id' (type number) with zero description coverage. The description adds no information about what the id references (event ID? external ID?), its format, or how it is used, so it entirely fails to compensate for the missing schema details.

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?

"Delete event" is a tautology of the tool name wealthbox.events.delete. It states the obvious without adding any specific scope, prerequisites, or distinguishing details beyond what the name already conveys.

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 provided on when to use this tool versus events.update, events.list, or other delete tools. There is no context about prerequisites, alternatives, or scenarios where deletion is appropriate.

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