Set Primary Patient Case

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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false, but the description confirms the mutation intent and importantly clarifies that changes are limited to primary status, not renaming or payer scenario. This adds beyond annotations.

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?

One concise sentence with clear action, parameter reference, and an exclusions note. Front-loaded with the purpose and usage.

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?

With a single parameter, full schema coverage, and no output schema, the description provides sufficient guidance: what it does, how to find the ID, and what it can't do. Minor gap: no mention of idempotency or potential side effects, but annotations cover idempotentHint.

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%, and the description reinforces the parameter's purpose ('to promote to primary') but adds minimal extra meaning beyond the schema's own description. 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?

Clearly states the verb 'promote' with the resource 'existing patient case' and specifies the operation is by case ID. Distinguishes it from other tools like tebra_update_patient by focusing on setting primary status.

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?

Explicitly instructs how to find case IDs via tebra_get_patient, providing a concrete usage path. Also lists exclusions (cannot rename or change payer scenario), which helps the agent avoid misusing the tool.

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