list_appointments

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

With no annotations, the description carries the burden of behavioral disclosure. It does state that the operation lists appointments, defaults date_from to today, and returns a list of dicts with known keys, which establishes a read-only intent. However, it does not define 'recent,' describe ordering, pagination, or status filtering, and the 'and more' tail is vague.

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 short and front-loaded with the core purpose, followed by a compact Args section and a Returns line. It has no filler, though the ambiguous 'recent appointments' phrasing could be made more precise without much extra length.

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?

For a single optional parameter and a tool with an output schema, the description is mostly sufficient: it documents the parameter and the shape of results. The main completeness gap is the lack of guidance around the sibling list_past_appointments, which leaves an agent unsure whether 'recent' overlaps with past appointments.

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 coverage is 0%, but the description compensates by specifying that date_from is an ISO date string (YYYY-MM-DD), acts as the starting point, and defaults to today. This adds real meaning beyond the bare nullable string in the schema, though it does not clarify null handling explicitly.

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 opens with a clear verb and resource: 'List upcoming and recent appointments.' It identifies the domain and time scope, but it does not distinguish this tool from the sibling list_past_appointments, and 'recent' is left undefined.

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?

There is no guidance on when to use list_appointments versus its sibling list_past_appointments, nor any exclusion criteria such as 'past appointments should be fetched with list_past_appointments.' The parameter note about starting from today implies a temporal usage, but the choice between tools is left entirely to inference.

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