delete_event

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful behaviors: it returns a confirmation dict with the deleted event's UID and summary and raises ValueError if the event is not found. It also implicitly signals destructiveness through the word 'Delete,' though it does not explicitly state permanence or side effects.

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 compact and well-structured: a one-sentence purpose, then concise Args, Returns, and Raises sections. Every part contributes useful information, and the core action is front-loaded.

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?

The description covers the essential invocation aspects: action, parameter semantics, return shape, and error behavior, which is sufficient for a simple two-parameter delete tool with an output schema. A minor gap is that it doesn't mention calendar_name is optional or has a default, but the schema provides that detail.

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 0% schema description coverage, the description fully compensates by explaining both parameters: uid is the unique identifier and calendar_name must be the full name with provider prefix. This adds real semantic meaning beyond the bare schema titles and helps the agent supply correct values.

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 opens with a specific verb ('Delete'), a resource ('calendar event'), and the identifying key ('UID'), making the tool's function immediately unambiguous. It clearly distinguishes from siblings like list_events, get_event, and update_event by focusing solely on deletion.

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?

The description gives no explicit guidance about when to use this tool versus alternatives such as update_event or create_event. It does not state exclusions or conditions, leaving an agent to infer usage solely from the verb 'Delete'.

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