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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the 7-day span constraint and date format, but both already appear in the schema, and it says nothing about permissions, pagination, or return shape. Useful but not rich behavioral context.

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?

Front-loaded and compact, with the resource and range constraint stated first. 'High-value booking-slot lookup' is filler and the raw endpoint path largely restates the already-documented parameters, so it is slightly padded.

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?

For a read-only, fully-documented 5-param tool with no output schema, the essentials are present. The gap is the unaddressed cliniko_next_available_time sibling, which an agent would plausibly confuse with this tool when choosing a booking lookup.

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 100%, so all five parameters are already documented, including the yyyy-mm-dd pattern and 7-day span. The description only restates the from/to format and span, adding no new parameter meaning; 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?

States a specific verb and resource ('List bookable appointment slots') and scopes it precisely to business + practitioner + appointment type within a date range. However, it does not differentiate itself from the sibling cliniko_next_available_time, which is the obvious alternative for booking-slot lookup, so it stops short of a 5.

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?

Usage is implied by the scoping ('within a date range', span <= 7 days), but there is no explicit when-to-use guidance or exclusion. The sibling cliniko_next_available_time is never named, so an agent gets no help choosing between a range listing and a next-slot lookup.

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