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

Annotations already cover the safety profile, yet the description adds substantial semantics: the response is the complete HTTP JSON body enumerating editions, facts, plans, conditions and sources; edition_key validates identity but does not filter or merge; unknown values and open bounds are passed through unchanged. This is exactly the kind of non-obvious behavior an agent cannot infer from readOnly/idempotent hints.

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?

Front-loaded with the core action and return shape, and every clause carries information (no-alias, no-inheritance, no-ranking, passthrough of unknown values). It is dense and jargon-heavy, requiring careful parsing, but not padded.

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?

With no output schema, the description supplies the return-shape contract itself (full JSON body with editions, facts, plans, conditions, sources, publication metadata) and covers the notable exclusions. Nothing an agent needs to invoke it correctly appears 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?

Schema coverage is 100%, so the baseline is 3 and the schema already documents both keys. The description nonetheless reinforces the counterintuitive contract that edition_key is a validation-only identity check returning the unchanged full product, and restates that aliases are not accepted for product_key.

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 (Read) and resource (versioned EHR product JSON projection) with the exact access path (exact product key), and explicitly contrasts with get_provider_detail for company profiles. An agent can distinguish this from search/match siblings without opening the schema.

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 rules out alias resolution, edition inheritance, calculation and ranking, and routes company-profile requests to get_provider_detail. It implies exact-key lookup versus search_providers but never states what to do when the key is unknown, so one alternative is left implicit.

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