calendar_search

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

With no annotations, the description carries full burden. It only mentions keyword search and date format, lacking details on result behavior (e.g., pagination, ordering, case sensitivity, or what happens if no results). This is insufficient for a mutation-ambiguous operation.

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 extremely concise: two clauses that front-load the core purpose (keyword search) and immediately specify parameter format. Every word is earned with zero redundancy.

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 no output schema and no annotations, the description is too sparse. It fails to mention return format, error handling, result limits, or how dates interact with keyword search. An agent would need to infer critical operational details.

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 0%, so the description must compensate. It provides the date format (YYYY-MM-DD) for begin_date and end_date, and clarifies that keyword is for searching. This adds essential meaning beyond the bare schema properties.

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 '按关键词搜索日程' (search calendar by keywords), which is a specific verb and resource. It also mentions date parameters, distinguishing this tool from sibling tools like calendar_get_events which list events without keyword 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 the tool is for searching calendar events by keyword and optionally by date range, but it does not explicitly state when to use this tool versus alternatives like calendar_get_events. No contextual guidance or examples are provided.

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