search_meetings

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

No annotations provided, so description carries full burden. It discloses filter combination logic (AND), default paginated list when no filters, date format (YYYY-MM-DD), and source for owner_id. Could mention pagination details or ordering, but overall transparent.

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?

Concise at 8 lines with front-loaded purpose. Every sentence adds value: filters, date format, resource for owner_id. No redundancy or fluff.

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 9 parameters, no required, and an output schema, the description covers core usage: filters, date constraints, owner_id source, and pagination. It lacks explicit mention of limit parameter and does not detail all date fields, but is sufficient for most use cases.

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 description must compensate. It clarifies date format for all date parameters and points to list_users for owner_id. However, it does not explain title, limit, or other parameters beyond general usage, leaving some gaps.

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?

Clearly states the tool searches for meetings by title, date range, or owner. Distinguishes from siblings like get_meeting (single) and log_meeting (create).

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 guidance to provide at least one filter for targeted results, notes AND logic, and explains behavior without filters. Also advises using list_users for owner_id. Lacks explicit when-not-to-use, but context is sufficient.

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