delete_event

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

With no annotations, the description must fully disclose behavior. It only states the basic action without mentioning consequences like irreversibility, side effects, or error conditions. This is insufficient for an agent to reason about safety and outcomes.

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 concise at a single sentence. While it could include more detail, it is not verbose and directly conveys the core action. It earns its place but could be restructured to front-load the most critical info.

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 delete-by-id operation with no output schema, the description covers the basic function. However, it lacks context on behavioral aspects and usage preconditions, which are relevant even for simple tools. It meets a minimum viable standard but feels incomplete.

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 already documents the 'id' parameter with a description. The tool description adds minimal value by restating 'by ID'. Since schema coverage is 100%, the baseline is 3, and the description does not significantly enhance understanding of 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 clearly states the action ('Delete') and the resource ('an event'), and specifies the identifier ('by ID'), which distinguishes it from sibling tools like delete_song or delete_venue. However, it is minimal and could be more precise about scope.

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, such as prerequisites (e.g., event must exist, user permissions) or when alternatives might be preferred. This leaves the agent without context for appropriate invocation.

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