DMEPOS fee schedule (state + modifier specific)

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the output shape changes with the presence of state, and the data source is the current CMS DMEPOS quarter, which tells the agent about data freshness.

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?

A dense but well-structured three-sentence description; the core lookup, the state/modifier behavior, the data source, and the exclusion each appear once with no padding.

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?

No output schema exists, so the description carries the burden of indicating what comes back, and it does describe exact per-state rates versus national ranges plus the data source. It could say more about return fields or units, but it is sufficient for correct invocation.

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 already documents the state exact-vs-national behavior and the RR/NU/UE modifier meanings, so the description largely restates what the schema provides. It adds only a slight interpretive gloss ('a modifier narrows the answer to rental or purchase'), consistent with the baseline 3 when the schema does the heavy lifting.

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 (look up the CMS DMEPOS fee schedule for a DME/orthotic/prosthetic HCPCS code) plus the domain boundaries (rental vs purchase, rural vs non-rural, per state). This clearly separates it from siblings like reimbursement_basic or code_reimbursement.

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?

Explains the operational choice between supplying a state (exact rates) versus omitting it (national min–max ranges), and gives an explicit exclusion: 'no professional-service (CPT) rates.' It does not name a specific alternative tool, which keeps it from a 5.

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