Move an event to another calendar

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

The annotations already mark the tool as destructive, and the description adds valuable detail beyond that: all IDs referencing the event stop working, a listing is needed to get the new ID, and the destination calendar may be visible to others. It does not explain the confirm_token confirmation flow, so it is not a perfect 5.

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 three sentences with no filler. The core behavior is front-loaded, and the identity-invalidation consequence is stated economically and clearly.

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 mutation, the description covers the most important consequences: the original event ID stops working, a new ID must be found via listing, and the destination may expose the event to other viewers. The confirm_token workflow is only hinted at through the schema, which is the main remaining gap.

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 describes all three parameters with 100% coverage, including that id must come from a listing tool and that destination_calendar_id accepts a path, URL, or final path segment. The description adds only the visibility caveat about the destination calendar, which does not meaningfully raise it above the high-coverage 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 description opens with a specific action on a specific resource: 'Copies an event into another calendar and removes it from the first.' This precisely defines move as copy-plus-delete and clearly separates it from siblings like create_event, update_event, and delete_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 gives clear context for when to use the tool: moving an event to another calendar, including to a calendar other people can see. It does not explicitly name alternatives or say when not to use it, but the copy-and-remove semantics make the intended use unambiguous.

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