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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds that no mutation path exists in the API and that this behaves like `appointment_list`. The field list also gives a useful preview of the response, which matters since there is no output schema.

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?

Two tight sentences, front-loaded with the payload description and followed by the read-only/mutation-location caveat. No filler.

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 tool with strong annotations, the description covers purpose, response shape, and the absence of write operations. Minor gaps remain around not-found behavior and whether paging or expansion is needed for related lead/conversation data.

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 single parameter has 100% schema description coverage and the schema already says the id comes from `appointment_list`, so the description cannot add much. It offers no format, length, or error semantics for `appointmentId` beyond what the schema states.

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?

States a specific verb and resource — full detail for one booked meeting — and enumerates what is returned (time, timezone, status, lead, conversation). This is clearly distinguishable from `appointment_list`, which it names explicitly.

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?

Explicitly frames the tool as read-only and tells the agent that rescheduling and cancelling happen in the web app, which is an effective 'do not use this for mutations' signal. It does not restate the lookup path to an id (that lives in the schema), so guidance is clear but not exhaustive.

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