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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real behavior: results are scoped to one location, sorted oldest-start-first, canceled excluded by default, and it discloses an auth requirement (Cotlet API key with app access). The auth note plus sort/scope disclosure is genuine value beyond annotations.

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-loads the core purpose and the exclusion rule before the auxiliary guidance. Mostly tight, though the 'Confirmation status is the one Meevo shows on the appointment' sentence is slightly redundant 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?

With no output schema, the description usefully enumerates the returned fields and ordering. Combined with the auth note and the sibling handoff, an agent has enough to call it correctly; only richer result-shape detail 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 coverage is 100%, so the baseline is 3. The description reinforces include_canceled semantics and the confirmation-status meaning, but adds little syntax or meaning beyond what the schema already documents for from/to/staff_id/location_id.

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) plus resource (appointments), scope (date range, Appointment Book, one location), and the fields surfaced (client, services, employee, confirmation status). It is clearly distinguishable from sibling reads like meevo_get_client and from the write siblings it names (reschedule/cancel_appointment).

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?

Explains the date-range/paging context and explicitly notes that canceled appointments are omitted unless include_canceled is true, and routes the appointment_id to reschedule_appointment/cancel_appointment. No explicit when-not-to-use, but the operating context is clear.

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