update_calendar_event

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

With no annotations, the description bears full burden. It mentions returning updated metadata or errors but lacks behavioral details such as whether partial updates are supported, idempotency, or required permissions.

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 concise with a clear main sentence followed by a bulleted list of arguments and return type. It is front-loaded with purpose, no unnecessary words.

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 all parameters and return format adequately for a basic understanding. However, lacking usage guidelines and behavioral transparency reduces completeness. It does not explain matching semantics or error handling beyond an error message.

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?

Despite 0% schema description coverage, the description adds meaning for all 7 parameters, explaining each with examples (e.g., 'identifier: Event id or title text' and 'start_datetime: Optional replacement start in YYYY-MM-DD HH:MM format').

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 updates a calendar event, specifying the verb 'Update' and resource 'Calendar event'. It distinguishes from siblings like 'create_calendar_event' and 'delete_calendar_event' by requiring an exact or uniquely matching 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 implies usage for updating events with matching criteria but does not explicitly state when to use this versus alternatives like search_calendar_events or list_calendar_events. No exclusions or context provided.

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