calendar_search_events

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

No annotations are provided, so the description carries the full burden. It adds useful behavioral detail by listing the fields searched (summary, description, location, attendees), but does not disclose response format, pagination, auth requirements, or default behaviors beyond what the schema already indicates. For a read-only search tool, this is moderate but not comprehensive.

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 two concise sentences with no filler. It front-loads the purpose and then adds search-scope detail in the second sentence. Every word earns its place.

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?

Given the tool's moderate complexity (6 params, 2 required) and no output schema, the description sufficiently defines the tool's core function. It could mention return value or default time range behavior, but the schema already documents most parameters, so the description is adequately complete for a search tool.

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 baseline is 3. The description adds no parameter-specific nuance beyond what the schema already provides (e.g., timeMin/timeMax, maxResults). It does not harm or further clarify the parameter meanings.

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's function with a specific verb ('Search') and resource ('Google Calendar events'), and specifies the search scope (summary, description, location, attendees). This distinguishes it from sibling tools like calendar_list_events, which lists events without text filtering.

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 implies when to use the tool: when you need to find events by text query across specific fields. It does not explicitly name alternatives or exclusion criteria, but the context is clear enough for an agent to differentiate it from the list/create/update event siblings.

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