Export events to a .ics file

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's main added value is the UTC serialization detail, which is genuinely non-obvious and useful for consumers. However, for a tool that writes a file, it omits key behavioral facts: whether an existing out_path is overwritten, whether the directory is created, and where the file is written relative to the caller.

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 action and immediately followed by the two selection modes and the timezone caveat. No filler or restatement of the title.

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 file-export tool with no output schema and full schema coverage, the description covers selection modes, output format, and timezone handling, which is most of what an agent needs. The remaining gap is file-overwrite/error behavior, which the annotations do not cover either.

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 five parameters including the from/to inclusivity, the calendar scoping with from/to, and the acceptable id sources. The description's 'pass either ids or a from/to window' adds the mutual-exclusion intent, but that is largely implied by the schema text, so baseline 3 is appropriate.

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: writing chosen events to a new .ics file, and clarifies the artifact is portable ('send or import elsewhere'). It is clear on its own, but does not distinguish itself from nearby siblings such as ics_create or the generic export_csv/report_export_csv, leaving the agent to infer which export path applies.

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?

Explicitly tells the agent the two ways to select data: pass ids (sourced from events_list) or a from/to window. That is actionable selection guidance. It stops short of when-not guidance, e.g. what to do when both are supplied or which mode to prefer for large ranges.

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