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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety bar is lower. The description adds genuinely useful context beyond that — the compliance-plan horizon date, the rate-label on plugging cost, and the explicit note that the Full Wellbore cross-check changes no outcome, count, or cost. It does not address cost/rate-limit or failure behavior for unknown operator numbers.

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 purpose is front-loaded, but the payload is one sprawling sentence with deeply nested parentheticals ('approaching by 2042-09-01 (compliance-plan horizon)', '(a cross-check only; ...)'), which is hard to parse. The information earns its place but the structure could be broken into a scope line plus a returned-fields list.

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?

An output schema exists, so return values need not be spelled out — yet the description's enumeration of claim counts, plugging cost, crossing schedule, and the cross-check caveat is accurate and helps the agent decide whether this tool answers the user's question. Only the absence of sibling routing keeps it from a 5.

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 already documents the six-digit format with leading zeros and an example. The description restates the same meaning without adding format, validation, or lookup semantics 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?

States a specific verb and resource: returns one operator's SB 1150 screening exposure from the publication, keyed by RRC operator number. It's clear what the tool produces, though it never explicitly contrasts itself with siblings like screen_operators or list_operator_wells.

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?

Usage is only implied by the resource ('one operator's ... exposure'). There is no statement of when to prefer this over screen_operators or get_well, and no prerequisites or exclusions are given.

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