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

With annotations all false and no readOnly/destructive/idempotency hints, the description carries the transparency burden. It discloses non-obvious behavior: the patient receives a confirmation code by email, the request is not sent to the clinic yet, and the whole flow happens 'without leaving the conversation.' It does not discuss repeat-call effects or failure modes, but the core side effects are clear.

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?

Three short sentences carry all essential information, with the action and key constraint front-loaded. There is no redundant restatement of the input schema or annotation fields.

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 tool is moderately complex, but the description covers when to use it, what side effects occur, and the key distinction that the clinic is not contacted. An output schema exists to cover return values, and practice_slug is the only thin spot across all required inputs.

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 description coverage is 67%; patient_name and patient_email are already documented in the schema, and the description only lightly reinforces them ('the code goes there'). practice_slug lacks a schema description and is only glossed as 'the selected clinic' in the first sentence. This partially compensates but does not fully explain how to obtain or format the slug.

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 ('Start an appointment request') and immediately differentiates this from the request-confirmation step by stating 'nothing reaches the clinic yet.' It also references the matching action name (xona_email_appointment_request), so an agent can distinguish it from siblings like confirm_dental_request.

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 an explicit trigger condition: 'Use it where list_dental_practice_actions marks xona_email_appointment_request as completes_in_conversation.' This tells the agent when to invoke this tool and ties it to a sibling discovery tool, leaving no ambiguity about selection.

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