simplepractice_list_appointments

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context beyond that: it explains the meaning of the two statuses (scheduled vs. requested) and mentions pagination ('Pages by number'). No contradiction with annotations; the description enriches the behavior profile.

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 concise—three short sentences with no fluff. The purpose is front-loaded, and every sentence adds value: the subject, the status semantics, and the pagination note. Excellent structure.

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 description covers the core behavior (listing appointments with status filter and pagination) but omits the compact parameter and pageSize details, which are present in the schema. For a read-only listing tool with no output schema, this is a reasonable but not exhaustive description; an agent might need to consult the schema for full parameter guidance.

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 50%, and the description adds meaning for the status parameter (explains the enum values) and hints at page usage, but it does not mention compact or pageSize. Since it partially compensates for the schema gaps, it earns a middle score.

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 clearly states the tool lists appointments from the Client Portal, with explicit meaning for the status values ('scheduled' vs 'requested'). It distinguishes from sibling list tools by naming the specific resource (appointments) and domain (Client Portal), making its purpose unmistakable.

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 gives clear context on how to use the status filter and mentions pagination, but it does not explicitly say when to use this tool over alternatives or provide exclusions. The usage is implied by the tool name and resource, but there's no direct comparison to siblings, so guidance is adequate but not explicit.

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