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

Annotations already provide readOnly/destructive hints; the description adds the list of action categories but does not disclose partial-failure behavior, recurrence scope implications, or side effects beyond the action list. It does not contradict annotations.

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 that efficiently communicates the core purpose without filler or redundancy.

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?

Despite having 10 parameters and no output schema, the description stays minimal. It doesn't address important contextual aspects like the 200-item cap, potential partial failures, or behavior of actions that require additional fields (e.g., assign). The rich schema compensates somewhat, but the description could provide more high-level guidance.

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 coverage is high (90%), so parameters are well-documented. The description adds no syntax or constraint details beyond what the schema provides, only mapping the action list. It meets the baseline without adding parameter-specific value.

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 tool performs a single bulk action across many calendar events, enumerating specific action types (shifts, reschedules, queue moves, cancellations, assignments). This distinguishes it from single-event update_calendar_event and bulk_schedule.

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 phrase 'many calendar events at once' implies the use case for bulk operations, contrasting with single-event tools. However, it does not explicitly mention when not to use it or point to alternatives like update_calendar_event for individual updates.

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