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

Beyond the readOnlyHint annotation, the description adds that cancelled appointments are included and differentiated via a status field, that results are ordered nearest first, and that authorization is required. This gives the agent actionable behavioral context beyond what the annotation conveys.

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 four short sentences, each providing essential information: purpose, cancellation behavior, use case, and auth requirement. There is no redundancy or filler, and the main purpose is front-loaded.

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 returned fields, ordering, cancellation inclusion, use case, and authorization. It doesn't explicitly state that past appointments are excluded, though 'current/upcoming' implies it, and the auth requirement is not detailed. Overall sufficient for a simple zero-parameter list tool.

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 tool has zero parameters, so there is no schema to elaborate on. Per the rubric, a baseline of 4 is appropriate when no parameters exist, and the description adds no unnecessary parameter detail.

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 the user's current/upcoming appointments with specific fields (booking_id, date, time, status) and ordering (nearest first). It distinguishes from sibling tools like list_past_bookings through the 'current/upcoming' scope and the explicit mention of cancelled appointments.

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 provides clear usage context by stating 'Needed to reschedule/cancel.' It also implies exclusion of past bookings via 'current/upcoming,' but does not explicitly name alternative tools or provide when-not-to-use guidance.

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