find_meeting_slots

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

With no annotations, the description carries the full burden. It discloses the free-tier slot limit, the paid endpoint behavior, weekend/holiday exclusion, and hints at the 'upgrade' field in the response. This provides valuable behavioral context beyond the schema.

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 two sentences. The first sentence packs the core functionality, and the second adds tier-specific behavior. No superfluous words.

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 description covers the key logic (overlap, working hours, weekends, holidays) and the free/paid tier distinction. It does not specify the exact response structure beyond mentioning 'upgrade', but given the lack of an output schema, it provides a reasonable overview for an agent to invoke the tool 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?

The input schema already describes all 3 parameters with 100% coverage. The description does not add significant new meaning to the parameters, only reiterates the country-based holiday exclusion, so baseline 3 is appropriate.

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 uses the specific verb 'Find' with a clear resource 'working-hour time slots that overlap across participants in different timezones'. It explicitly states the purpose and differentiates from sibling tools like convert_timezone by focusing on overlap calculation rather than single-time conversion.

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 presents a clear scenario for use: scheduling a meeting across participants in different timezones. However, it does not explicitly name alternatives or state when not to use the tool, so it stops short of providing full usage guidance.

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