search_events

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful operational detail beyond annotations: the endpoint, cross-account/calendar scope, time-range bounds, and that results begin with title/summary. It does not contradict annotations.

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 compact and front-loaded with the core purpose, then gives a usage trigger and key parameter details. Each sentence contributes useful information, though the endpoint string is somewhat redundant with the tool's function.

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?

There is no output schema, and the description only hints at return content with 'Title/summary first.' It does not explain pagination, result limits, or response shape beyond that. For a moderately complex search tool with annotations covering safety, this is adequate but not fully complete.

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 0%, so the description must carry parameter meaning. It explains time_min/time_max as ms epoch and accounts_json as an array with accountId and calendarIds, which is valuable. However, it leaves query, limit, and user_time_zone unexplained, so parameter semantics are only partially compensated.

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 does full-text search of events across accounts/calendars in a time range, using a specific verb and resource. This distinguishes it from sibling tools like get_events, which imply list/retrieve behavior rather than keyword search.

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 gives an explicit trigger: 'Call when the user asks to find meetings by keyword.' This gives clear context for when to select the tool, though it does not explicitly contrast it with alternatives such as get_events or list-style browsing.

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