clear_calendar

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

With no annotations provided, the description carries full burden. It mentions destructive behavior ('Delete ALL events') and the primary calendar constraint, but omits details on reversibility, required permissions, rate limits, or impact on recurring events.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and constraint.

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?

Given the tool's destructive nature, the lack of annotations, and three undocumented parameters, the description is severely incomplete. It does not cover return values, success/failure indicators, prerequisites, or behavior on recurring events.

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 0%, yet the description adds no meaning for any parameter. It does not explain the purpose of 'account' or 'password' parameters, leaving the agent without guidance on their usage.

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 it deletes all events from a primary calendar, with the specific verb 'Delete ALL events' and resource 'primary calendar'. This distinguishes it from siblings like delete_event (single event) or create_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?

The description includes the constraint 'only works on a primary calendar', implying not to use on non-primary calendars. However, it does not explicitly state when not to use or suggest alternatives like delete_event for partial removal.

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