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

readOnlyHint=true already tells the agent this is a safe read. The description adds the HTTP verb/resource and the half-open date-window semantics (starts_from inclusive, starts_to exclusive via the q[] operators shown in schema), which is modest extra context. It says nothing about pagination behaviour, result caps, or rate limits beyond what the schema fields imply.

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?

Two tight sentences: the operation and its filter surface come first, the endpoint follows as a compact anchor. No filler, no repetition, nothing that does not earn its place.

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 zero-required-parameter list tool with a fully described schema, a readOnly annotation and no output schema, the description covers operation, filters and endpoint adequately. The only real gap is pagination/ordering guidance, which is partially mitigated by the page/per_page/sort/order fields being self-describing in the schema.

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 every parameter is already documented inline, including the ISO 8601 format and the q[] operator mappings. The description restates the filter set and the starts_from/starts_to pair but adds no syntax or semantics beyond the schema, so the baseline 3 applies.

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 (List) and resource (individual appointments), enumerates the filter dimensions, and names the underlying REST resource GET /individual_appointments. An agent can distinguish this from cliniko_get_appointment (single fetch) and cliniko_create_appointment without opening any schema.

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 by listing optional filters (patient/practitioner/business/type, starts_at window), which tells the agent what this tool is for, but it never states when to prefer it over siblings such as cliniko_list_available_times or cliniko_next_available_time, nor any preconditions. Usage context is implied rather than explicit.

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