calendar_update_event

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

Discloses key behavior: 'Only provided fields are changed' (partial update). Lists all parameters with their effects. Missing error conditions and return details, but no annotations to contradict. Good overall transparency.

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?

Structured with concise sentences and an Args list. No wasted words; front-loaded with purpose. Efficient and easy to parse.

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?

Covers usage hint, partial update behavior, and all parameters with formats. Lacks error handling info and return value description, but output schema likely addresses return values. Very complete given complexity.

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 has 0% description coverage; description fully compensates by explaining all 7 parameters with clear semantics (e.g., 'New event title (omit to keep unchanged)'). Adds significant value beyond schema types.

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?

Clearly states 'Update an existing calendar event' with specific verb and resource. Distinguishes from siblings like calendar_create_event and calendar_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?

Explicitly advises to use calendar_get_event first to see current values, providing clear context for usage. Does not explicitly exclude alternatives but implies proper workflow.

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