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

Annotations already carry readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are ordered newest first and booking/session notes are deliberately excluded from the payload.

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?

Dense and front-loaded: purpose and returned fields first, then the exclusion, then filters, then the endpoint. Every sentence carries information, though the trailing 'GET /consultant/sessions.' is of limited value to an agent.

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 what is omitted, and the schema documents pagination cursors. It stops short of describing the response envelope (next_page cursor flow) an agent needs to page through results.

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 every parameter (including the before_id/after_id cursors and the group boolean) is already documented in the schema. The description restates the filter categories and adds the ordering fact, which only marginally exceeds 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?

States a specific verb and resource ('List sessions (appointments)') and enumerates the fields returned, which separates it from the singular practice_better_get_session. It does not explicitly name a sibling alternative, so it falls just short of the top score.

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 filter enumeration ('date range, practitioner, client record, service or group/1-1') gives context for how to narrow results, but there is no when-to-use guidance relative to practice_better_get_session for a single appointment, and no explicit exclusions.

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