Teladoc MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool cancels an appointment, implying a destructive mutation, but lacks details on permissions needed, whether cancellations are reversible, confirmation requirements, or any side effects (e.g., notifications sent). This leaves significant gaps for safe agent use.

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 a single, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 tool's complexity (a destructive mutation with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It doesn't cover behavioral traits, parameter details, or expected outcomes, leaving the agent with insufficient information to invoke it correctly and safely.

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 description doesn't mention parameters at all, and schema description coverage is 0% (no descriptions in the schema). However, with only one parameter ('appointment_id'), the baseline is 4, but it's reduced to 3 because the description adds no semantic context (e.g., what format the ID should be or where to find it), missing an opportunity to compensate for the schema gap.

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 ('Cancel') and resource ('a Teladoc appointment'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'book_appointment' or 'list_appointments' beyond the verb, which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., needing an existing appointment), exclusions (e.g., cannot cancel past appointments), or how it relates to siblings like 'book_appointment' or 'list_appointments'.

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