Renvoie par email au patient le lien de gestion de son rendez-vous. À utiliser si le appointment_token n'est plus disponible côté client. Le token n'est jamais renvoyé dans la réponse — uniquement par email au patient.
| Name | Required | Description | Default |
|---|---|---|---|
| patient_email | Yes | Email du patient enregistré lors de la réservation. Doit correspondre exactement. | |
| appointment_id | Yes | Identifiant unique du rendez-vous |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the token is never returned in the response and is only sent via email, which is critical behavior beyond the annotations. Annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) do not contradict this. The description adds valuable context about side effects.
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 two sentences long with no wasted words. It conveys the purpose, when to use, and key behavioral detail efficiently.
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?
Given the simplicity of the tool (no output schema, only two parameters), the description is complete. It explains the action, condition for use, and what the response does not contain. No gaps remain.
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 already covers both parameters with descriptions (patient_email must match exactly, appointment_id is unique). The description does not add additional parameter semantics beyond the schema, and schema coverage is 100%, so 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?
The description clearly states the action: 'Renvoie par email au patient le lien de gestion de son rendez-vous.' It uses a specific verb ('renvoie') and resource ('lien de gestion'), and the context of when the token is lost distinguishes it from siblings.
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 explicitly says to use this tool when the appointment token is no longer available on the client side. While it doesn't explicitly mention when not to use or list alternatives, the sibling tools (booking, cancelling, etc.) are clearly different actions, so the guidance is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: booking, cancellation, rescheduling, searching for available slots (differentiated by scope), retrieving appointment details, listing appointments, resending tokens, and searching doctors. No ambiguity between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., book_appointment, find_next_available). This makes the API predictable and easy to use.
With 10 tools, the server is well-scoped for a medical appointment booking system. Each tool serves a necessary function without redundancy or excessive granularity.
The tool set covers the full appointment lifecycle: searching doctors and profiles, checking availability, booking, canceling, rescheduling, retrieving appointment details, listing appointments, and resending tokens. No obvious gaps for the intended domain.
