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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful default that an omitted patient_id searches only the baseline-adult Bundle, but it says nothing about the scenario edge cases the enum implies (rate-limited, consent-revoked, source-unavailable), which are behavioral traits an agent should know.

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?

A single tight sentence front-loaded with "Use this to", with the default-scenario caveat folded into a parenthetical. Efficient and well-structured, though the parenthetical slightly buries the most decision-relevant detail.

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?

An output schema exists, so return values need not be described, and the annotations cover the safety profile. The description covers scope and the default subject adequately; the only gap is guidance on sibling selection and the notable scenario variants (rate-limited, consent-revoked) that could change agent expectations.

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% and both parameters are fully documented with enums, so the schema does the heavy lifting. The description reinforces the patient_id default (baseline-adult) but adds no format or syntax detail beyond what the schema already provides, making the baseline 3 correct.

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: retrieve all resources of one FHIR R4 type for one scenario's patient. It is clear what the tool does, but it does not explicitly differentiate itself from the many per-type siblings (get_demo_conditions, get_demo_allergies, get_demo_labs), leaving the agent to infer that this is the generic cross-type variant.

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?

"Use this to get all resources of one FHIR R4 type" implies the usage context but gives no when/when-not guidance relative to the sibling shortcuts that fetch the same data per type. No exclusions or alternative routing are stated, so the agent must infer whether to prefer this or a specific get_demo_* tool.

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