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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added value is the returned-field list, which matters because there is no output schema; it says nothing about behavior when the id doesn't exist or what access is required.

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?

There is zero waste and the resource is front-loaded, but the single sentence fragment has no verb and is terse to the point of under-specification for a tool an agent must select among 35 siblings.

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 one-parameter read with full schema coverage and complete safety annotations, the essentials are present, and the field list partially compensates for the missing output schema. Missing details about not-found behavior and access prerequisites keep it at minimum viable rather than complete.

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 100% for the single required parameter, and the schema itself explains the origin ('Appointment id from list_appointments') plus a numeric pattern. The description adds nothing beyond that, so the baseline 3 applies.

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 fragment 'One appointment: client, services, team member, times, status, price and notes' identifies a single-resource retrieval and enumerates what comes back, which implicitly distinguishes it from the list_appointments sibling by scope ('one' vs list). It lacks an explicit verb like 'retrieve', so the operation must be inferred from context rather than stated.

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 no when-to-use guidance and names no alternatives. The routing hint ('Appointment id from list_appointments') exists only in the schema's appointment_id property, not in the description, so the description itself offers no usage logic.

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