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 it delivers richly: it states the tool is 'Read-only; no side effects, auth, or rate limits', discloses timezone handling ('UTC times, no VTIMEZONE needed'), and specifies the return shape ('{ics, event_count}'). This goes well beyond the bare minimum and fully compensates for missing 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?

Three sentences cover safety, format, use case, timezone behavior, and return type without redundancy. The read-only note is front-loaded, and every sentence carries distinct information. No wasted 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?

For an export tool with no output schema, the description fully explains what the agent needs to know: the operation type, the output format and its quirks (UTC, no VTIMEZONE), the return payload, and the intended use. Required parameters are described in the schema, and the description does not omit critical behavioral information.

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 parameters (from, to, entity, calendar_name) are already documented in the schema. The description adds no additional parameter-level detail beyond the window concept already expressed in the schema. Baseline 3 applies because the description does not degrade or add meaningful semantics.

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 names a specific verb ('Export'), a resource ('events in a window'), and a concrete output format ('RFC 5545 ICS calendar'). It also states the intended downstream use (import into Outlook/Calendar apps), which distinguishes it from sibling tools like calendar.events.list. There is no ambiguity about what this tool produces.

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?

The description gives clear context for when to use the tool: 'for import into Outlook/Calendar apps' and 'Export events in a window'. It does not explicitly name alternatives or exclusions, but the use case is specific enough that an agent can infer when this is appropriate. A slight deduction for not explicitly contrasting with calendar.events.list or mentioning that it is not for general event listing.

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