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

Annotations already declare destructiveHint=true, so the mutation warning is not novel, but the description adds valuable context: it writes to the connected EHR/PMS, advises a confirmation GET, and names the POST /patients endpoint. It does not cover auth requirements, rate limits, or duplicate-patient behavior.

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 sentences, front-loaded with the verb and mutation warning. Every sentence adds useful information, including the write target and a confirmation step. There is no filler or repetition.

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?

There is no output schema, but the description partially compensates by advising a GET to confirm the created patient. The mutation, external system, and endpoint are covered. Duplicate-handling guidance for a patient-creation tool is missing, but required parameters are fully documented in the schema.

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 all 10 parameters are already documented in the input schema. The description adds no parameter-level format or constraint details beyond what the schema provides. This meets the baseline of 3 when the schema does the heavy lifting.

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 states a specific verb and resource: CREATE a new patient record in a location. It is clearly distinguishable from siblings like get_patient, search_patients, list_patients, and update_appointment. No ambiguity remains about what the tool creates.

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 create context is clear, but there is no explicit guidance on when to use this instead of alternatives or when not to use it. It does not mention checking for existing patients with search_patients or using an update path for existing records. 'GET the patient back to confirm' is post-call workflow, not tool-selection guidance.

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