calendar_search_events

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

The description adds a meaningful behavioral note that partial reads produce partial search results, which is relevant given the openWorldHint annotation. The readOnly and destructive safety aspects are already covered by annotations, and the description supplements these with search-specific behavior without contradicting them.

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 directly communicates the core operation, search matching behavior, and an important partial-read caveat.

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 lack of an output schema, the description provides sufficient context for the main input behavior and warns about partial reads. It does not cover error cases, sorting, or timezone handling, but those are not essential for basic invocation and the core semantics are clear.

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?

The schema has minimal parameter descriptions (only calendarId is described), so the description partially compensates by explaining query semantics and the bounded/selected calendar view. However, it does not explicitly clarify start, end, accountId, or limit beyond what their names and schema constraints imply.

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 literal, case-insensitive search over calendar event subject and bodyPreview fields, within an explicitly selected and bounded calendar view. This distinguishes it from listing or fetching events, especially given the sibling calendar_list_events tool.

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 (text-based search on event subject/bodyPreview) but does not explicitly contrast it with alternatives like calendar_list_events or calendar_get_event. It provides some context by describing the search semantics, but lacks direct 'use this instead of X' guidance.

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