manage_out_of_office

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

No annotations, so description carries full burden. It discloses side effects: 'mutating actions may auto-decline existing/incoming invites based on auto_decline_mode.' It also notes OOO events live on primary calendar and require 'calendar.events' OAuth scope. Lacks rate limits but covers key behaviors.

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?

Description is concise with three key sentences: purpose, sibling distinction, and side effects/requirements. It front-loads the purpose. Slightly verbose with the side effects paragraph, but 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?

Complexity is high (14 params, output schema exists). Description covers purpose, sibling tools, side effects, scope, and calendar placement. It does not detail return values, but output schema handles that. Missing maybe an example usage, but overall sufficient.

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 value beyond schema: it explains that OOO events auto-decline invitations and that calendar_id must be primary (echoed in param description). Also clarifies that start_time/end_time can accept date-only strings. Provides context for action parameter.

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?

Description clearly states 'Create, list, update, or delete Out of Office events,' using a specific verb and resource. It distinguishes itself from siblings 'manage_event' and 'manage_focus_time' by explicitly naming them as alternatives for normal events and focus-time blocks.

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?

Description provides explicit guidance: 'For normal events use manage_event; for focus-time blocks use manage_focus_time.' It also explains when OOO events appropriate (auto-decline, presence change). However, it lacks explicit 'when not to use' beyond the sibling references.

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