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

Beyond the read-only annotations, it discloses returned fields, ordering ('latest first'), a cap of 100, and that procedure counts are included but medical detail is not. It does not discuss permissions or pagination, but those are minor for this read-only list operation.

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?

Three sentences are front-loaded with the use case, then return shape, then exclusions. There is no redundant wording and every sentence adds useful selection or behavioral information.

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 rich annotations, full schema coverage, and an output schema, the description covers when to call it, what comes back, ordering, limits, and what it must not be used for. Nothing essential for correct invocation is missing.

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 the input schema already documents limit, time range, clinicId, and patientId thoroughly. The description confirms the two main query modes but adds little parameter-level meaning beyond what the schema provides.

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 states a specific verb and resource: listing appointments by patient or by clinic/day. It also clearly separates this tool from related needs such as counting busy days and retrieving procedure names or medical detail.

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 gives explicit when-to-use guidance ('when someone asks when a patient is booked, or what is booked at the clinic on a given day') and clear exclusions. It does not name the specific alternative tools, so an agent still has to infer which sibling handles counting or procedure details.

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