Add calendar events

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

Discloses that it writes data and requires calendar:write scope, aligning with annotations (destructiveHint=true). Adds constraint that all events in one call must be in the same year. No contradictions with 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 compact (two sentences plus key clarifications), front-loaded, and every sentence adds value without 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?

Covers main points: multi-event capability, year constraint, type handling, required scope. No output schema, but description doesn't need return values. Could mention success behavior or error handling, but overall sufficient given annotations.

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 100%, baseline 3. Description adds: 'Set type="custom" together with custom_day_off_type_id from officient_list_event_types; omit that id for sick_day / education' and 'duration_minutes may be the string "all_day"', providing extra semantics beyond schema.

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 adds one or more events (day off, sick day, education, overtime, etc.) to a person's calendar. It specifies constraints like all events in same year and differentiates from sibling tools like overwrite and delete.

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?

Provides context on when to set type='custom' and when to omit custom_day_off_type_id, and mentions required scope. However, it does not explicitly say when not to use this tool or compare with alternatives like overwrite or delete.

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