Search Meetings

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavior beyond that: it returns compact summaries, and explains how related_to and related_to_type can be used in app URLs. This gives the agent insight into output meaning and follow-up actions.

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?

Three focused sentences. The first states purpose; the second gives a key filter guidance; the third explains output usage. No filler or 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?

With 13 optional parameters, an output schema, and read-only annotations, the description covers the essential guidance: handling large result sets, filtering by owner, and using related entity fields. The existence of an output schema means return values need not be described. This is complete for the tool's complexity.

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 the baseline is 3. The description adds value by highlighting owner_id with a concrete use case (scoping to a user) and pointing to list_users for ID resolution. It also clarifies the paired usage of related_to and related_to_type, which is helpful beyond the schema.

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 states a clear verb and resource: 'Search Recruit CRM meetings'. It also specifies the output type ('compact summaries designed for large result sets'), which distinguishes it from mutation tools like create_meeting and update_meeting.

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 practical usage context, advising to filter by owner_id and resolve IDs via list_users. It also implies this tool is for large result sets ('compact summaries'). However, it does not explicitly name alternatives or exclusion conditions, so it falls short of a 5.

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