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

With no annotations, the description carries the full behavioral burden. It does not state whether deletion is permanent or reversible, what permissions are required, or what happens to the event's attendees/notifications. 'Delete' signals a destructive mutation, but nothing beyond that is disclosed.

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?

A single short sentence, front-loaded with the action. It is efficient, though the 'Run Google calendar action:' prefix is boilerplate that earns little.

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 annotations and no output schema, the description should cover irreversibility, identification of the target event, and required permissions. None of that is present, and the lone 'detail' parameter gives an agent no reliable way to specify which event to delete.

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?

Schema description coverage is 100%, so the single 'detail' parameter is documented in the schema and the baseline is 3. The description adds no meaning about how the event to delete is identified, which is the key semantic gap, but per the high-coverage rule a 3 is the appropriate baseline.

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 phrase 'delete event' gives a clear verb+resource and implicitly contrasts with siblings add_event and update_event. However, 'Run Google calendar action:' is filler that restates the tool's namespace, and there is no scope detail (which event, by what identifier), so it stays at minimum-viable rather than distinctive.

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 this should be used versus calendar__update_event or calendar__add_event, and no stated prerequisites (e.g., need an existing event id). Deletion is only vaguely implied by the word 'delete'.

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