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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by noting the fixed fictional sample and that all resources of a single FHIR type are returned, but it does not mention pagination, rate limits, or any quirks beyond that. There is no contradiction with 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 sentence, front-loaded with 'Use this to', no filler. It earns its place by naming the action, object, and source in a single pass.

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?

The tool is low-complexity (one required enum param, one optional fixed param) and has an output schema plus strong annotations. The description, schema, and annotations together tell an agent what to pass and what to expect, so no additional explanation is required for correct invocation.

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?

The schema covers all parameters with descriptions, including the enum of FHIR resource types and the optional fixed patient filter, so the description does not need to repeat them. It adds no new parameter-level detail, but at 100% schema coverage the baseline score of 3 is appropriate.

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 names a specific action ('get all resources'), a precise target ('one FHIR R4 type'), and the data source ('FinchNode's fixed fictional sample EMR'). This makes it easy to tell apart from the sibling get_demo_* tools, which are organized by clinical category rather than by FHIR type.

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 opening 'Use this to' gives a clear purpose: retrieve all resources of one FHIR R4 type, which signals when this general search tool is appropriate. It does not explicitly mention sibling alternatives or state when not to use it, but the intended context is unambiguous and no exclusions are needed given the fixed demo scope.

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