listAppointments

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not mention that this is a read-only operation, nor does it explain pagination behavior, default ordering, or how filters like personId affect results. The minimal description leaves the agent to infer semantics from the name alone.

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 concise two-word phrase, with no filler or redundancy. While it is refreshingly brief, it borders on under-specification, missing an opportunity to convey essential context in a structured way.

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?

Given the lack of annotations, absence of an output schema, and the presence of many related list tools, the description is incomplete. It does not state what is returned (e.g., an array of appointments), how pagination works, or when to prefer this tool over listEvents or listAppointmentTypes. This makes the tool harder to invoke correctly in a broader workflow.

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?

The input schema describes all four parameters (next, limit, offset, personId) with complete coverage. The description itself adds no parameter-specific detail, but since the schema already covers them, a baseline score of 3 is appropriate.

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 'List appointments' uses a specific verb and resource, clearly indicating the operation. It distinguishes from sibling tools like listAppointmentTypes and listAppointmentOutcomes by referring to the base 'appointments' resource, though it could be confused with listEvents or listCalls without further context.

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?

No guidance is provided on when to use this tool versus alternatives such as listEvents or listAppointmentTypes. The description simply states the action without any context, exclusions, or comparisons to sibling list tools.

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