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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world hints. The description adds useful behavioral context beyond that: the data is a fixed fictional sample, no authentication is needed, and the content spans encounters, appointments, and care teams normalized from FHIR R4. This meaningfully supplements the structured hints without contradiction.

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 compact and well-structured. It opens with the primary purpose, adds important data-source and authentication context, and closes with a clear routing instruction to a sibling tool. No sentence is wasted.

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 parameterless read-only tool with a rich output schema and strong annotations, the description covers everything an agent needs: what data is included, its source, the fact that no auth is needed, and when to choose an alternative tool. Nothing critical is missing.

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 tool has zero parameters, so the description has no parameter semantics to explain. The schema is empty and the description provides all necessary context about what the tool returns, satisfying the baseline for parameterless tools.

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 clearly states the tool's function: getting only visits/encounters from FinchNode's fixed fictional sample EMR. It distinguishes itself from get_demo_health_record by explicitly noting it returns only visits, and clarifies the data is normalized from FHIR R4 Encounter, Appointment, and CareTeam.

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 explicitly says to use this tool when you want only visits, and names get_demo_health_record as the alternative when visits are needed alongside other categories. It also notes that no account or API key is required, giving clear and actionable usage context.

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