calendar_find_free_slots

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

No annotations are provided, so the description carries full burden. It mentions 'available time slots' but doesn't disclose behavioral traits like whether it considers user availability, meeting room resources, timezone handling, authentication needs, or rate limits. For a calendar tool with zero annotation coverage, this leaves significant gaps.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, though this brevity contributes to gaps in other dimensions.

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 the tool's moderate complexity (3 parameters, calendar operations), no annotations, but with an output schema (which handles return values), the description is minimally adequate. However, it lacks context about whose calendar, availability criteria, and integration with sibling tools, leaving room for improvement.

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 the description must compensate. It mentions 'in a range' which hints at window_start and window_end, but doesn't explain duration_minutes or provide any format details (e.g., ISO timestamps). The description adds minimal value beyond the bare parameter names.

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 'Find available time slots in a range' clearly states the verb ('Find') and resource ('available time slots'), but it's vague about scope and lacks differentiation from sibling tools like calendar_list_events. It doesn't specify whose calendar is being checked or what constitutes 'available'.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like calendar_list_events and calendar_create_event, there's no indication of when this free-slot finding tool is appropriate versus listing existing events or creating new ones.

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