Get an appointment

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by explaining that attendeeIds enable guest additions and per-attendee cancellation, and that status indicates whether the booking is active—meaningful semantics beyond a generic read.

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 compact: three sentences, front-loaded with the primary action, followed by the most useful field semantics. Every sentence adds information beyond the schema and none is redundant or promotional.

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 simple single-resource read tool with an output schema and safety annotations, the description covers the meaningful returned fields and their implications. It lacks only an explicit note on when to prefer this over list_appointments or get_todays_appointments, which is a minor omission given the leading phrase 'one appointment.'

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 provides only a bare 'appointmentId' string with 0% schema description coverage. The description does not explain the expected format, origin, or acceptable values of appointmentId; it only implies that the parameter selects the appointment via 'one appointment.' Since the description must compensate for low schema coverage and does not, this is a clear gap.

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 specific verb and resource: 'Return full detail for one appointment,' and enumerates the exact fields returned (status, attendees, attendeeIds, hosts, location, notes). This clearly distinguishes it from list-oriented siblings like list_appointments and get_todays_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 phrase 'full detail for one appointment' establishes that this is the tool for fetching a single appointment's comprehensive data rather than a list. It does not explicitly name alternatives or provide exclusions, so it stops short of a 5.

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