calendar_search

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds 'capped' (implied limit) and 'read-only' (redundant but consistent). It does not disclose that search is limited to metadata only, nor does it explain output behavior. Overall, minimal added value beyond 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 a single sentence of 9 words, which is concise but insufficiently structured. It fails to cover multiple important aspects (e.g., parameter details), so it is under-specified rather than efficiently comprehensive.

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?

Despite an output schema existing, the description does not mention return values or structure. Four parameters exist, but only one is hinted at. The tool's complexity (search with date ranges) is not addressed, leaving significant gaps for an AI agent to use it correctly.

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 explain parameters. It only mentions 'by title' for the query parameter, but ignores limit, days_back, and days_forward. 'Capped' loosely relates to limit but is not explicit. No guidance on date ranges or the meaning of these 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 verb 'Search', the resource 'local Calendar event metadata', and the method 'by title'. It also adds 'capped and read-only' for scope. This distinguishes it from sibling search tools like notes_search or contacts_search, as it specifically targets calendar events.

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?

No explicit guidance on when or when not to use this tool versus alternatives like calendar_get_event. The description only implies usage for title-based searches but does not mention scenarios where other tools are more appropriate.

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