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

Annotations declare it is not read-only, not destructive, not idempotent and closed-world, so the safety profile is already covered. The description adds genuinely new behavior: a verification code is emailed to the patient first and the request is only sent after confirmation, and the request may go out by email or the clinic's web form. It stops short of stating failure modes (e.g., invalid code, repeat invocation).

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 dense sentences with no filler, front-loading what the tool does before the two-step flow and the routing condition. The parenthetical delivery detail is somewhat heavy but earns its place.

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?

An output schema exists, so return values need not be explained. For a non-idempotent mutation that triggers email sends, the description covers the side-effect sequence and the routing rule well; only edge-case behavior and re-invocation semantics are unaddressed.

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 67%, so most parameters are already documented; the description reinforces that patient_email is where the code goes and implies practice_slug is 'the selected clinic'. It adds no format or constraint detail beyond the schema, so the baseline 3 is appropriate.

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 ('Start an appointment request') and clarifies the delivery mechanism (email or the clinic's own website form). It also distinguishes itself from the sibling confirm_dental_request by describing the two-step flow, so an agent can tell the two apart without opening schemas.

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?

Gives an explicit activation condition ('Use it where list_dental_practice_actions marks xona_email_appointment_request as completes_in_conversation') and names the follow-up tool confirm_dental_request. The when-to-use rule and the next step are both stated rather than inferred.

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