calendar_export_ics

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

With no annotations provided, the description carries the full burden and does so well: read-only, no side effects, no auth, no rate limits, UTC times so no VTIMEZONE is needed. It also discloses the return shape (`{ics, event_count}` with a JSON string field), which is essential given there is no output schema.

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?

Three tight sentences, front-loaded with the safety/behavioral profile before the format and return details. Every clause earns its place; nothing is repeated from structured data.

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?

For a no-annotation, no-output-schema read tool, the description covers safety profile, output format standard, timezone handling, intended consumer, and return shape. An agent has everything needed to call it and interpret the result.

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 description coverage is 100%, so the schema already documents all four parameters with types and semantics (ISO 8601 with timezone, entity filter, X-WR-CALNAME default). The description adds only the generic notion of a 'window' and does not extend meaning beyond the schema. Baseline 3 is correct here.

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?

States a specific verb and resource: export events in a window as an RFC 5545 ICS calendar. The namespaced 'calendar_export_ics' plus the explicit output format makes it instantly distinguishable from calendar_events_list and the entity CRUD siblings.

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?

Gives clear context for when this is the right tool: producing an importable ICS file for Outlook/Calendar apps. It stops short of naming the alternative (calendar_events_list) for simply inspecting events, so the routing decision is implied rather than explicit.

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