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

Annotations already mark the tool as readOnlyHint: true and idempotentHint: true. The description adds valuable context: it 'clears confirmed bookings AND each Space's listed hours' and mentions 'truncation flags mean UNKNOWN beyond the page', which explains pagination behavior. No contradictions with annotations.

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 brief yet informative. Each sentence serves a purpose: stating the main function, explaining what is cleared, listing optional filters, and noting boundaries (31 days, truncation). No wasted 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 parameters, boundaries, and behavioral notes (truncation flags). With no output schema, it could explain the return format better, but the core logic and constraints (e.g., max 31 days, min 15 min duration) are adequately described.

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 carries the full burden. It lists all parameters (required: community_id, duration_minutes, date_from, date_to; optional: space_id, location_name, min_capacity, limit) and their roles. However, it does not provide format details (e.g., date format) or deeper semantics beyond naming.

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 it finds open bookable gaps across spaces, specifying inputs (duration, date range) and what it filters out (confirmed bookings and space hours). It uniquely distinguishes itself from sibling tools like list_spaces or check_space_availability by focusing on availability gaps.

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 explicitly lists required and optional parameters, mentions the maximum date range of 31 days, and indicates it is read-only. However, it does not explicitly state when to use this tool versus alternatives (e.g., check_space_availability), leaving some ambiguity.

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