search_meetings

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

No annotations are provided, so the description must cover behavioral traits. It discloses the 30-day limit and disabled transcript search, but does not mention authentication needs, rate limits, pagination, or result ordering. The performance warning is useful but insufficient for full transparency.

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 sentences, each earning its place: first states purpose and fields, second adds critical usage constraints. No redundant or vague language. Front-loaded with the core action.

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?

The tool lacks an output schema, yet the description does not mention what the search returns (e.g., a list of meeting objects, limited fields). It also does not specify the maximum number of results or sort order. Given the low complexity (2 params) and absence of output schema, the description should provide more details about the response format to be 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 100%, so baseline is 3. The description adds context by mentioning the search fields (titles, summaries, action items) and the performance note about transcript search, which aligns with the schema descriptions. No additional syntax or usage details are provided beyond what the schema already states.

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' and the resource 'meetings', specifying the fields (titles, summaries, action items) and the 30-day time constraint. It implicitly distinguishes from sibling tool 'list_meetings' which likely returns all meetings 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?

Provides explicit context: searches only last 30 days and transcript search is disabled by default for performance. While it doesn't explicitly state when not to use or name alternatives, the context is clear enough for an agent to decide against using it for older meetings or when transcript search is needed.

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