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

Annotations only declare destructiveHint=true, so the description's 'MUTATES DATA — writes to the connected EHR/PMS' and the 'POST /patients' endpoint add real context about what the write touches and how. It still omits auth requirements, duplicate handling, and whether creation is idempotent, which would matter for a mutating tool, but the added mutation scope goes beyond the annotation.

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?

Four short, front-loaded fragments with no filler; the create/mutate intent leads. The trailing 'POST /patients' is an implementation detail an agent cannot act on, which is the only slightly wasted token.

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 10-parameter mutation tool with no output schema, the description covers intent and mutation scope but not the return shape (the new patient id the agent needs for the confirm step) or duplicate-prevention guidance. Adequate but with clear gaps for a write operation on clinical records.

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%, with required flags and format patterns (e.g., date_of_birth yyyy-mm-dd) already documented per parameter. The description adds no parameter-level detail beyond echoing the location scoping, so the schema carries the load and the baseline 3 applies.

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 ('CREATE a new patient record in a location'), which cleanly separates it from the read-oriented siblings nexhealth_get_patient and nexhealth_search_patients. The scope (a location) and the write nature are unambiguous.

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?

It gives a follow-up step ('GET the patient back to confirm'), which implies the intended workflow, but never says when to use this versus alternatives. Critically, it omits the standard precondition for patient creation — checking nexhealth_search_patients first to avoid duplicate records — leaving the agent to infer it.

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