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

readOnlyHint=true already establishes the safety profile, so the description's added value is the disclosure of the returned payload ('client, services, staff, state and cancellation'), which matters because there is no output schema. It stops short of describing pagination behavior or result ordering.

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 scope statement is front-loaded in the first sentence and the return-payload list is compact. The trailing 'GraphQL: appointments.' mapping is a small but legitimate addition; overall there is no filler.

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 list tool with a fully documented 5-parameter schema and no output schema, the description covers scope, optional filters, and the shape of each returned appointment. Missing only minor operational details like pagination semantics, which the schema partially covers via 'after'/'first'.

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%, including a detailed QueryString grammar for 'query' and format notes for client_id and location_id, so the schema already carries the parameter burden. The description only restates the high-level filtering intent (client, date range, staff member) without adding syntax or constraints beyond the schema, matching the baseline.

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 gives a specific verb and resource ('List appointments') plus its scope: one location, optionally one client, filterable by query. This implicitly separates it from the singular sibling boulevard_get_appointment, but it never names or contrasts with that sibling explicitly, so it falls short of the top mark.

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?

It conveys the common narrowing axes ('optionally for one client and filtered by a query such as a date range or staff member'), which implies when the filters are useful. However, it gives no explicit when-to-use/when-not guidance and no routing to alternatives such as boulevard_get_appointment for a single appointment.

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