add_to_calendar

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), description discloses native confirmation dialog on macOS and local attachment saving. Provides key behavioral context for mutation without destructiveness.

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?

Multiple sentences but every sentence adds value. Front-loaded with purpose, then details in logical order. No redundancy or filler.

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?

Description covers platform specifics, extraction behavior, return values, and key parameters. With 7 params and no output schema, it provides sufficient context for an agent to select and invoke correctly.

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%, so baseline is 3. Description adds moderate value by tying parameters like confirm, save_attachments, and alarm_minutes to overall behavior, but does not add meaning beyond schema for most params.

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 it adds an email event to local calendar (macOS Calendar.app / Linux via xdg-open), automatically extracts event data, and specifies return values. Distinguishes well from sibling tools like extract_calendar or list_events.

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 explains when to use (adding calendar event from email) and what it does automatically, but lacks explicit alternatives or when-not-to-use guidance. Sibling extract_calendar exists but is not compared.

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