calendar_find_available_slots

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

With no annotations provided, the description takes full responsibility for behavioral disclosure. It states it returns up to 20 sorted slots, explains constraints (working hours/days), and defines search window. It covers the key behaviors for a read-only scheduling tool.

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 front-loaded with a clear purpose sentence, followed by a structured Args block. It is slightly long but no redundant sentences. Every sentence adds value.

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 7 parameters and presence of an output schema, the description covers search constraints and result characteristics (up to 20 sorted slots). It omits the structure of returned slots, but the output schema likely handles that. Still, a brief mention would improve completeness.

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 explain parameters. It lists all 7 parameters with descriptions (e.g., 'ISO 8601 start of search window') beyond the schema titles. However, 'calendar_id' is vaguely described as 'Calendar name or URL path', which could be more precise.

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 tool finds available (free) time slots for scheduling new events. This verb+resource purpose distinguishes it from siblings like 'get_freebusy' (which shows busy blocks) and 'search_events' (which finds existing events).

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 usage for scheduling new events but does not explicitly contrast with sibling tools or state when not to use. For example, it doesn't suggest using 'get_freebusy' for checking busy times. The purpose is clear enough for an agent to infer context.

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