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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the bar for additional disclosure is lower. The description usefully adds that this is a keyless public record, names the return payload fields including the total count and breakdowns, and clarifies the basin coverage. It does not discuss rate limits or response size limits beyond the schema's limit parameter, but the added context is substantive.

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 longer than the minimum but every sentence carries information: resource, differentiator, return fields, use cases, geography, and filtering guidance. The basin mention (Anadarko/SCOOP/STACK) is slightly tangential to invocation but still helps the agent understand scope. It is efficiently structured and front-loaded.

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?

With no output schema, the description carries the burden of explaining return values, and it does so thoroughly: operator, status, well type, well name, county, location, total count, and breakdowns. It also covers authentication (keyless), filter recommendations, and geographic scope. Nothing critical is missing for an agent to decide whether and how to call this tool.

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%, so the parameter semantics baseline is 3. The description repeats the filter names and recommends using at least one of them, which is mildly useful, but it does not add meaningful meaning beyond what the schema already documents for each parameter.

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 opens with a specific verb and resource: 'Search Oklahoma oil & gas wells', then names the exact filters (county, operator, API, well type) and the data source (OCC RBDMS). It also differentiates itself from a pure map layer by enumerating the returned fields, making its purpose unmistakable even among many siblings.

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 gives concrete use cases ('who operates wells in county X', 'how many wells does operator Y have') and recommends at least one of county, operator, or API to narrow results. It implicitly excludes map-layer use cases, but it does not name a specific sibling alternative or state an explicit when-not-to-use condition.

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