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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new operational context: a 2 MB body cap, a 10 calls-per-minute rate limit, and a hard prohibition on real patient data, plus the note that findings refer to a synthetic Bundle. It stops short of describing failure modes or what happens when the size/rate limits are exceeded.

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?

Four short sentences, front-loaded with the purpose and then the operational constraints; nothing is padded. Slightly telegraphic phrasing ('Findings describe a synthetic Bundle') costs a little clarity.

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 no explanation, and the annotations carry the safety profile. What remains an agent needs to call this correctly — the data policy, size cap, and rate limit — is all 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 coverage is 67% and the schema already documents the bundle object as synthetic-only and constrains ig to the PAS IG. The description adds only the 'synthetic payloads only' injunction, which duplicates the schema's bundle description, and says nothing about valid values for the vague 'version' parameter.

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: validate a synthetic Da Vinci PAS Submit Bundle with the named ImOnFHIR validator. That is clearly distinct from the sibling tools (compare_*, explain_finding, search_digest), though the description never explicitly contrasts itself with any of them.

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?

Usage is implied by the verb 'Validate' on a PAS Bundle, and the 'Synthetic payloads only' constraint effectively bounds the domain of applicability. There is no explicit when-to-use/when-not framing or routing to any alternative tool, so guidance is adequate but inferential.

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