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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds the date-range scope and the returned fields, but it does not explain pagination behavior, response shape, or any operational constraints beyond what annotations and schema already provide.

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 description is a single compact sentence with no filler or repetition. The date-range scope and key fields are front-loaded and easy to scan.

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?

The schema is rich and fully described, and annotations carry the safety profile, so an agent can call the tool correctly. However, the description is sparse for a list operation: it does not clarify pagination, sorting, or how this relates to sibling appointment tools, leaving some contextual 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 description coverage is 100%, so all seven parameters, including from, to, limit, cursor, status, client_id, and team_member_id, are already documented in the schema. The description adds only the general notion of date-range filtering and returned fields, not parameter syntax or format details beyond the schema.

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 identifies the resource (appointments), the date-range scope, and key returned fields such as client, service, team member, price, and status. It is clear enough to distinguish a ranged list from a single-record lookup, but it does not explicitly name or contrast itself with siblings like get_appointment or find_available_slots.

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?

The description implies usage when appointments are needed within a date range, but it gives no explicit guidance on when to use this tool versus get_appointment, find_available_slots, or other appointment-related siblings. There are no stated exclusions, prerequisites, or alternative-selection rules.

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