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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), lowering the bar. The description adds essentially nothing behavioral beyond that — no note on result-size caps, how n interacts with max_rows, or cost/latency for large rankings. It is adequate only because the annotations carry the safety story.

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 compact sentences, front-loaded with the capability statement followed by a concrete example. No filler, though the example consumes a fair share of a short description that could have spent that space on parameter meaning.

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 described, and annotations cover safety. However, for a 15-parameter tool with only 33% schema coverage, the description omits default ordering, the n/max_rows distinction, and filter-combination behavior, leaving real gaps 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 description coverage is only 33% across 15 parameters, so the description should compensate but largely does not. It restates enum values already in the schema and gives one example payload, leaving n, orden, max_rows, provincia, empresa, cuenca, area_concesion, yacimiento, formacion and the n-vs-max_rows relationship unexplained.

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 (rank / 'top N') and enumerates the rankable resources (wells, areas, companies, fields, basins, formations) and ranking metrics (production, BOE, GOR, water cut, growth, new wells, IP30/90/180 variants). This is clearly distinguishable from the sibling query_* tools, which retrieve data rather than produce ordered rankings.

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: the 'Top N ... by ...' framing and the worked example suggest when to reach for it, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. execute_sql or query_production for raw rows). The agent must infer the boundary against siblings.

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