search_events

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavior beyond annotations: case-insensitive matching across specific fields and a default date window. It omits result limits/pagination and how the calendars filter interacts with the search.

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?

Two tight sentences with no filler; the search scope is front-loaded and the default range follows immediately.

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 a read-only search tool with no output schema, the description gives the essentials: matching semantics and default time bounds. It could be more complete by explaining the calendars filter and any result-size limits, but nothing critical to invocation 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 coverage is 50%: start/end are documented, while query and calendars are not. The description compensates well for the central query parameter by explaining which fields are searched and case-insensitivity, and it clarifies the default time range tied to start/end. The calendars array remains unexplained.

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?

States a specific verb and resource ('Find events') and specifies the matching fields (title, location, description) and case-insensitivity. This clearly distinguishes text search from list_events and get_event.

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?

Provides clear context for use via the query-based search and the default time window (90 days back to 365 days ahead). It does not explicitly name alternatives such as list_events or state when not to use it, but the purpose implies the right usage.

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