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

The annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is clear. The description adds useful context: it writes to the live Halaxy account, always creates a new record, carries duplicate risk, and gives the underlying POST endpoint.

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?

The description is front-loaded with the key write/create behavior and duplicate-avoidance instruction. Every sentence adds actionable information, including the org parameter guidance and endpoint, 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 create mutation with rich schema coverage and annotations covering the safety profile, the description supplies the critical missing operational context: live-write warning, duplicate-avoidance workflow, and managing_organization guidance. It does not describe the response shape, but no output schema exists and the core invocation guidance is otherwise complete.

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 most parameter meaning is already documented. The description adds value for managing_organization by explaining it is the practice group id, giving an example (PG-12345), naming its source tool, and describing when to pass it.

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 uses a specific verb and resource: 'Creates a new patient record.' It also states that this always creates a new record, which distinguishes it from the sibling list/search tools such as halaxy_list_patients.

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 explicitly tells the agent to search with halaxy_list_patients first to avoid duplicates. It also gives a concrete condition for using managing_organization, sourced from halaxy_list_organizations, and clarifies that this tool is for creation rather than lookup.

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