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

Annotations already establish readOnlyHint=true, and the description adds genuinely useful behavior beyond that: the mandatory date/since/date_range constraint and the fact that results are paged with `next`/`previous` links. It omits rate limits or default page-size behavior, but the paging disclosure is real added value.

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 with the purpose, then the hard constraint, then optional filters and return shape – four tight sentences with no filler. Slight redundancy in restating the date/since/date_range rule that the schema already carries.

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?

With no output schema, the description steps in to explain the paged return envelope (`next`/`previous`), and it covers the required-parameter rule and all filtering dimensions. Only minor gaps remain (default page size, ordering), which are low-stakes for a read-list 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?

Schema description coverage is 100%, so formats, defaults, and the exclusivity rule are already fully documented in the schema. The description reiterates the one-of-three requirement but contributes no syntax or edge-case meaning beyond it, matching the baseline 3.

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?

Clear verb+resource: 'List appointments', reinforced by the underlying endpoint GET /appointments. It is distinguishable from the other list_* siblings by resource, though it does not explicitly contrast itself with any of them.

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 surfaces the key selection constraint imposed by the API – that one of `date`, `since`, or `date_range` must be supplied – and lists the optional narrowing filters (doctor, patient, office). It stops short of naming an alternative tool or explaining when a different listing approach would be preferable.

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