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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely new behavioral guarantee ('Every option has a booking_url') and the payload breadth, but says nothing about missing/invalid treatment_id behavior or how location inputs change the returned clinics and reviews.

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?

A single dense sentence, front-loaded with the resource, with no filler. It is list-like but every clause names a distinct section of the payload, so little could be cut without losing content.

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 the lengthy return-value enumeration is largely redundant, while the genuinely ambiguous behavior — whether clinic_id/near/place filter the clinics list and reviews, and whether they affect the option list — goes unaddressed for a 5-parameter tool with a nested object.

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 100%, so the schema already documents near, place, locale, clinic_id and treatment_id, including 'near wins over place'. The description mentions option_id, price and booking_url, but those are response fields rather than inputs, so it contributes little input-side meaning 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 title supplies the verb ('Get one treatment') and the description enumerates exactly what the single-treatment payload contains (procedure, recovery, sessions, options, clinics, reviews). This clearly separates it from search_treatments and get_clinic, though the description itself never names those 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?

Use is only implied: you fetch a treatment you already have an id for. It never says when to call this instead of search_treatments (which presumably also returns treatment data) or list_offers, and it gives no condition for supplying near/place vs clinic_id.

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