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

readOnlyHint=true already declares the safe-read profile, so the bar is lower. The description adds useful context by naming the return format (FHIR Bundle) and the underlying $everything operation, but it does not disclose payload size expectations, pagination behavior beyond _count, or any rate limits.

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 short sentences with the core action front-loaded, followed by the endpoint and optional scoping. Every sentence is useful, though the explicit FHIR path is slightly redundant with the tool name and endpoint convention.

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 simple read-only tool with no output schema, the description adequately covers the return type (FHIR Bundle) and the optional scoping controls. It could say more about what 'comprehensive' includes or how paging links work, but the essential call context is present.

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 the schema fully documents patient_id, _since, and _count. The description repeats the existence of _since and _count but adds no format, syntax, or edge-case 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?

States a specific verb and resource ('Fetch the comprehensive record for a patient as a FHIR Bundle') and adds the exact FHIR endpoint, so it is distinguishable from simpler siblings like get_patient or list_* by scope. However, it never explicitly names an alternative, so it falls short of the sibling-differentiating 5.

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 gives no when-to-use guidance or alternatives; it only notes optional scoping parameters. An agent must infer that this is the comprehensive read path versus get_patient or start_patient360_query, which is exactly the kind of inference the rubric penalizes.

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