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

Annotations indicate read-only, idempotent, and non-destructive behavior, which the description reinforces with 'Read-only' and elaborates on the return types (available, hard, soft) and local-time ranges. This adds value beyond annotations by explaining booking semantics (first approval wins) and the soft-listed hours verdict.

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 sentence that efficiently communicates the main purpose and key details, but the use of a semicolon to list statuses makes it slightly dense. It is front-loaded with the primary action.

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 explains the return values (available, hard, soft, soft-listed-hours verdict) and mentions local-time ranges, providing a solid understanding of the output. Without an output schema, this level of detail is adequate for a query tool.

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 description lists the four required parameters and specifies that times should be in ISO format, but does not clarify what community_id and space_id represent or the expected format of the time strings beyond ISO. Since schema description coverage is 0%, the description provides basic context but lacks depth.

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 checks venue space availability for a specific time slot, with explicit details on booking statuses (hard, soft) and verdicts. It distinguishes itself from sibling tools like 'list_bookings' by focusing on availability checking rather than listing all bookings.

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 lists required parameters (community_id, space_id, start_time, end_time) and implies it should be used before booking, but it does not explicitly state when not to use this tool or suggest alternative tools for other scenarios.

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