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 real behavioral context beyond that: the mandatory date/since/date_range constraint and the paginated return shape (`next`/`previous`), which the annotation does not convey.

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?

Short, front-loaded sentences that put the core action first and the key constraint second. The trailing 'DrChrono API: GET /appointments' line is largely redundant with the tool name and title, costing a point.

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 usefully discloses the paginated return shape and the required date constraint, covering what an agent needs before calling. It omits page_size/page defaults and error behavior, leaving minor gaps.

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 coverage is 100%, so all eight parameters are already documented in the schema. The description restates the same constraint and filter names without adding format detail (e.g., what `since` accepts versus `date_range`), so 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 and resource ('List appointments'), which cleanly separates it from create_appointment and the get_patient siblings. It does not explicitly name which sibling to use instead under what conditions, so it falls 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?

Gives the hard usage constraint (at least one of `date`, `since`, or `date_range` is required) plus the narrowing filters (doctor, patient, office), which tells an agent how to call it correctly. It stops short of stating when to prefer this over sibling list tools or what to do when results are empty.

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