calendar_search_events

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe, idempotent reads. The description adds value by noting the 366-day range cap and advising to narrow it for large calendars, which are behavioral traits beyond what annotations provide. No contradictions.

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 a single, front-loaded sentence of 14 words. It conveys the core purpose and constraints without redundant or extraneous information. Every word contributes value.

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 tool is read-only with 5 parameters (3 required) and no output schema. The description covers the key search constraints but omits details about the return format (e.g., list of matching events) and any pagination or sorting. It is mostly complete but could be slightly more explicit about what the search returns.

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 80%, which is high, so a baseline of 3 is appropriate. The description does not add parameter-level meaning beyond what the schema already covers (e.g., endDate cap is mentioned in schema). No new semantic enhancements for parameters.

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 clearly states the tool performs a search of events by summary text within a bounded date range. The verb 'Search' and resource 'events' are specific, and the constraints (summary text, date range) distinguish it from sibling tools like calendar_list_events (which lists all events) and calendar_get_event (single event by ID).

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 specifies the tool is for searching by text with a date range, but it does not explicitly state when not to use it or mention alternatives. The context of 'bounded date range' implies when to apply, but no guidance on exclusion or comparison with sibling tools is provided.

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