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

The destructiveHint=true annotation already signals the risk profile, and the "DESTRUCTIVE:" prefix is consistent with it. The description adds the transport details (POST /patients) and required field list, but those required fields and the date format are already fully documented in the schema, so the net new behavioral context is thin.

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?

Three dense clauses, no filler, and the destructive warning plus core action are front-loaded ahead of the input requirements and endpoint. Every sentence earns its place.

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 no output schema, the description omits what is returned (e.g., a new patient id/object), duplicate-patient behavior, and any permission requirements. It is adequate to invoke the tool but leaves meaningful gaps for a write operation.

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 a regex pattern for date_of_birth, so the schema already carries parameter meaning. The description's field list and "yyyy-mm-dd" note merely restate the schema; 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?

"Creates a new patient record" is a specific verb+resource that distinguishes it from the read-oriented siblings (list_patients, get_patient) and from create_appointment. It does not name a sibling explicitly, but the resource noun is 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?

The description states required inputs and the underlying endpoint but gives no when-to-use guidance, no prerequisites (e.g., doctor id must exist), and no exclusions relative to alternatives. An agent gets no help deciding when this tool is the right call.

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