Validate a FHIR resource

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

Description confirms the operation is read-only (no save), aligning with readOnlyHint annotation. It adds behavioral context about the endpoint and required structure (resourceType), surpassing annotation detail.

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?

Two concise sentences, front-loaded with purpose and endpoint. No redundant or filler content.

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?

Lacks description of the return value (e.g., OperationOutcome). While sufficient given no output schema, adding expected response type would improve completeness.

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?

With 100% schema coverage, schema already defines the param. Description adds critical constraint that resource must include resourceType, which is not in schema description, enhancing clarity.

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 validates a FHIR resource against server profiles without saving, using a specific HTTP method and endpoint. It distinguishes from sibling tools like search or read by focusing on validation.

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 advises using this tool before create_fhir or update_fhir to catch errors early, providing clear context for when to use it over alternatives.

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