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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds a genuinely useful interpretive caveat that counts are raw BSEE records and unadjusted for operator size or activity. It does not describe the return shape or ordering ties, which is the remaining gap.

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?

Two sentences, front-loaded with the ranking purpose followed by the important caveat, with no filler. 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?

For a simple two-parameter read tool with annotations covering safety, the description is adequate, but with no output schema it never states what a result row looks like (operator identity plus count) or how ranking ties/ordering are handled. That leaves the return contract to inference.

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 description coverage is 100%, and the schema already documents both 'sort' values and the 'limit' default/max, so the baseline is 3. The description merely restates the sort options already present in the schema without adding format or behavior detail.

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 specific verb and resource ('Ranks offshore oil and gas operators') and scopes it to BSEE incidents of noncompliance with the exact ranking dimensions. This clearly separates it from sibling search tools like bsee_search and other 'worst/top' rankers such as chemical_accident_worst or fails_to_deliver_top.

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 states what the ranking measures but gives no guidance on when to choose this tool over bsee_search or other BSEE-related siblings, and no exclusions or prerequisites. The enumeration of sort options is parameter detail, not usage guidance.

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