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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: a metered/paid access model gated on a Tensorust enterprise key, a free tier triggered by cell size or preview=true, and the 'Data only' disclaimer scoping it to raw reference data. It does not state behavior on empty cells or sort direction.

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 scoping triple (code, payer, state) is front-loaded and the returned-field list follows, so the reader gets the essentials first. The first sentence is a long run-on that packs rankings, fields, and fee math together, but almost every clause carries information.

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 correctly carries the burden of describing return values — determinations, median winning multiple, 2026 fee, expected fee cost, certification status, and the gap to the cell's overall loss rate. It is thorough for a lookup tool, though it omits what happens when no entity has decided the cell and the direction of the ranking.

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 75% and code, payer, and state already carry inline descriptions, so the schema does most of the work. The description does add real meaning for preview, explaining that preview=true unlocks free access, which the bare boolean in the schema does not convey. It says nothing extra about payer or state beyond the schema.

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 concrete verb and resource — it returns every certified IDR entity that decided a given CPT/HCPCS + payer + state cell, ranked by provider loss rate, and enumerates the returned fields. An agent can tell exactly what comes back. It does not distinguish itself from the related idr_offer or idr_scorecard siblings, which keeps it at 4 rather than 5.

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?

It supplies useful decision context — the initiating party proposes an entity and the other side has 3 business days to object, and the call is free when a cell has under 50 determinations or when preview=true, otherwise it needs a Tensorust enterprise key. That tells the agent how to access it cheaply but never says when to choose this over idr_offer or idr_scorecard, so usage against alternatives is only implied.

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