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

With no annotations provided, the description carries the full burden. It discloses the ranking basis and the included counts, but the term 'recent' is vague and no recency window, data source, or caveats about the results are mentioned. It is a read-oriented description, but lacks behavioral nuance.

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 single, efficient sentence that front-loads the core purpose and includes the key ranking and data details. Every phrase contributes meaning, and there is no redundant wording.

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?

The description covers the essential return content: ranked operators, state filter, and per-operator counts. However, it does not state the recency window for 'recent permits', explicitly confirm the response is a list, or address `limit` semantics. Given the lack of annotations and output schema, this is adequate but incomplete.

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 0%, so the description must compensate. It maps 'Texas or Oklahoma' to the `state` parameter, but it never explicitly explains the `limit` parameter or clarifies how many operators will be returned. The word 'top' hints at a limit, but the agent must infer this from the schema's default value.

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 states a specific verb ('Get'), a specific resource ('top oil & gas operators'), a geographic scope ('Texas or Oklahoma'), and a ranking criterion ('ranked by total well count'). It is clearly distinguishable from siblings like get_top_producing_wells or get_operator_permits.

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?

The description implies when to use this tool: when you need top operators by well count for TX/OK. However, it never explicitly names alternatives or says when not to use it, so the agent must infer the differentiation from the ranking metric and sibling tool names.

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