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

Annotations already declare it read-only, idempotent, and non-destructive, yet the description goes further by disclosing the comparison methodology: each line is checked against Medicare's rate, hospital lines use the outpatient facility rate plus the doctor's part and say 'compared_with', and it lists the specific question categories returned. This is substantive behavioral context beyond the structured 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?

Purpose is front-loaded and the return behavior follows logically. The paragraph is dense and re-states the title ('Check several lines of an itemized bill at once') and the example could be trimmed, but every sentence carries useful information, so it is efficient rather than 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 carries the return burden and does so by naming outputs (per-line comparison, totals, questions_to_ask categories, compared_with) and the hospital-bill special case. An agent has everything needed to invoke it and interpret results.

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 schema documents all five params and the baseline would be 3. The description adds meaning by restating the line format ('code, optional x and units, then the amount') and by explaining how setting/billed_by change the comparison, which meaningfully enriches the otherwise self-sufficient 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?

States a specific verb and resource ('Check several lines of an itemized bill at once') and the 'at once' scope distinguishes it from the single-value sibling medbillcheck_check_price. An agent can tell what it does and its batch nature 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?

Gives a clear triggering context ('when someone reads out or pastes several lines from an itemized bill') reinforced with a concrete multi-line example. However it does not name an alternative (e.g. check_price) or state when-not to use it, so it stops short of the 5 bar.

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