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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the tool's scope (county-level rankings) and the specific metrics included, which is useful. However, it does not disclose whether this is a read-only operation (though 'Get' implies it), whether results are sorted in a particular order, or how the 'limit' parameter affects the ranking output. The description is adequate but not rich in behavioral context.

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 description is a single sentence that front-loads the core purpose ('Get county-level drilling activity rankings') and then lists the specific data points. It is concise and every phrase adds value. It could be slightly more structured (e.g., separating the ranking criteria from the geographic scope), but it is efficient and readable.

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 tool with only 2 parameters (one required enum, one optional integer with defaults), the description covers the main purpose and the geographic scope. However, with no output schema and no annotations, the description does not explain the return format, the ordering of results, or how the limit parameter interacts with the ranking. An agent could call it correctly with the state parameter, but might be uncertain about the exact output structure or the meaning of 'rankings' in terms of sorting.

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 for the schema's lack of parameter documentation. The description mentions 'Texas or Oklahoma' which maps to the state enum, and 'rankings' implies the limit parameter controls how many counties are returned. However, it does not explain the exact meaning of 'limit' (e.g., top N counties) or the format of the state values beyond what the enum already provides. The description adds some context but leaves the limit parameter's semantics partially implicit.

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 clearly states the tool's purpose: 'Get county-level drilling activity rankings for Texas or Oklahoma' and lists the specific data points returned (total wells, recent permits, recent spuds, DUCs, top operator, top formation). This is a specific verb+resource combination that distinguishes it from sibling tools like get_county_production or get_duc_inventory.

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 usage context by specifying the geographic scope (Texas or Oklahoma) and the county-level granularity, which helps an agent know when to select this tool over state-level or operator-level siblings. However, it does not explicitly state when to use this tool versus alternatives like get_county_production or get_state_snapshot, nor does it mention any exclusions or prerequisites.

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