InviteKit Calendar Files

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

Beyond annotations, the description discloses concrete outputs: a downloadable RFC 5545 .ics file with time zone data, four add-to-calendar links, the first 5 dates in the event zone and optional attendee zones, and daylight saving changes flagged. It also clarifies what the tool does not do (send invitations, read or change calendars, track RSVPs), which is valuable behavioral context even though readOnlyHint and destructiveHint already cover safety.

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?

The description is dense but front-loaded: it opens with the primary use case, then summarizes inputs, outputs, and exclusions. Given the complexity of 13 parameters including recurrence and time zones, every sentence contributes useful selection or invocation guidance.

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?

The description is complete for a complex generation tool: annotations establish read-only, idempotent, non-destructive behavior; the schema fully documents parameters; an output schema exists; and the description covers use cases, inputs, outputs, limitations, and sibling alternatives.

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 input schema already documents all parameters thoroughly. The description summarizes key inputs such as title, local start/end, time zone, all-day dates, location, description, link, organizer, reminders, and recurrence details, but it does not add syntax or constraints beyond what the schema provides. Baseline 3 is appropriate when the schema carries the detailed parameter 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 states a specific verb and resource: generating a calendar invite, .ics file, or add-to-calendar links for one event or one repeating event. It names concrete event types and explicitly distinguishes this tool from the sibling generate_event_series, so an agent can identify its purpose without opening the schema.

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?

It gives explicit when-to-use guidance: when the user wants a calendar invite, .ics file, or add-to-calendar link for one event or one repeating event. It also gives exclusions: does not send invitations, read/change calendars, or track RSVPs; do not use for a list of different sessions (use generate_event_series) or for finding a meeting time across zones.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description still adds genuinely new behavioral context by naming the non-capabilities (no per-session add-to-calendar links, no invitations sent, no changes to anyone's calendar) and by describing the dual output (one .ics plus a dated list). It stops short of discussing size/time-zone validation failures or the rejected-input path, keeping it at 4 rather than 5.

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?

The trigger condition is correctly front-loaded, and the when-not sentence is placed last as a routing chaser. A few facts are duplicated from the schema (the 1-40 session cap, the session field list), which costs a little, but nothing is padding.

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 8-parameter generator with full schema description coverage, annotations and an output schema, the description supplies exactly what structured fields cannot: user-intent routing, sibling disambiguation, and explicit non-capabilities. Nothing an agent needs in order to choose or call this tool is missing.

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 every parameter is already documented in detail, including the start/end/duration_minutes relationship and the all_day flag. The description only restates the parameter grouping (per-session fields plus shared time zone, location, details, link, organizer and reminders) and the 1-40 cardinality, adding no semantics the schema lacks. Baseline 3 is correct.

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 states a specific verb and artifact: produce one .ics file containing several distinct events at once, with a concrete enumeration of scenario types (course schedule, training program, conference agenda, fixtures, webinars). The second paragraph clarifies the two-part resource (sessions + shared defaults) and the two-part output, so the tool is distinguishable from a single-event generator without reading the schema.

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?

Opens with an explicit triggering condition ('Use this when the user wants one calendar file (.ics) that adds several different events at once') and closes with an explicit exclusion plus the named replacement: 'Do not use for an event that repeats on a regular pattern (use generate_calendar_event with recurrence).' Both the when and the when-not are stated rather than inferred.

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