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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint false), so the description's added value is the cost model and result composition: the call is free, the full calibration file is sold by invoice, and the no-argument call returns broader tables. That upsell and the two-mode behavior are genuinely beyond the structured fields. It says nothing about pagination or result size, which keeps it from a 5.

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?

Everything is crammed into one long semicolon-chained sentence with a dense metric list; the key fact (entity scorecard, or arbitrator table when no domain) is front-loaded, but the list of metrics is hard to parse and would scan far better as bullets. Little is wasted, but the structure works against comprehension.

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?

There is no output schema, so the description has to carry the return contents, and it does: it names both result modes and the metric families in each. What remains unstated is the return container/format and how a caller should treat unmatched domains, but for a single optional-parameter read tool this is close to sufficient.

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% and the single parameter is already documented as 'Email domain of the filer or payer as the CMS file records it'. The description mostly restates that and supplies illustrative examples, without adding format rules (bare domain vs email, case handling, unknown-domain behavior). Baseline 3 is appropriate.

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+resource: a Q4 2025 IDR scorecard for one filing organization or payer, enumerated with the exact metrics returned (disputes, win rate vs the 85% provider norm, arbitrator fees, overreach shares, worst cells, arbitrator mix). It also carves out the no-domain mode, which produces a different result set, so an agent can tell what this tool does and what shape the answer takes.

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?

Gives clear routing on the one branch that matters: supply a domain to get an entity scorecard, supply nothing to get the arbitrator propensity table plus the 500+ dispute lists. Real example domains (fam-llc.com, uhc.com) show the expected input. It does not name a sibling or state when a different entity-level tool (e.g. idr_entity_pick) should be preferred, so it stops short of full alternative routing.

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