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

The description reinforces the destructiveHint annotation with 'WRITE' and goes further by emphasizing this creates a 'REAL' appointment in the 'live' practice, highlighting real-world side effects. It also discloses the defaulting behavior for ends_at, which annotations do not cover.

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 tightly written sentences plus the endpoint identifier carry all essential information. The WRITE stance, required parameter list, default behavior, and endpoint are each presented once with 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 mutation tool with complete schema coverage and a destructiveHint annotation, the description provides everything needed to invoke it correctly: required IDs, ISO 8601 timing, the ends_at default, and the live-practice consequence. No output schema exists, but the absence of return-value detail does not impede correct invocation.

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 100%, so the schema already documents every parameter including ISO 8601 format and the ends_at default. The description mainly restates the required parameter set and the default, adding no new semantic detail beyond the schema.

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 'WRITE — books a REAL new individual appointment', naming a specific action and resource, and distinguishes it from the sibling create_patient. It also specifies the endpoint POST /individual_appointments, leaving no ambiguity about what the tool does.

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 context is clear: use this when actually booking a live appointment, as opposed to fetching or listing appointments or checking availability. It does not explicitly name alternatives or say when not to use it, but the create/list distinction in the sibling set makes the intended use obvious.

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