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

With no annotations, the description carries the behavioral burden. It discloses the data fields, date range, coverage (~25 states), and license (CC BY 4.0), which is useful. However, it omits error handling, pagination, response format, and explicitly states it's a read-only operation (though 'Get' implies it). This is adequate but not thorough.

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 concise (three sentences), front-loads the primary purpose, and includes only relevant details: data fields, date range, coverage, license, and a pointer to a sibling for coverage. No fluff or redundancy.

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 query tool with no output schema, the description provides the expected fields and time range, which is helpful. However, it doesn't clarify the response structure (e.g., array of monthly records), ordering, or behavior for invalid inputs. The pointer to list_production_states mitigates coverage uncertainty, but gaps remain.

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 baseline is 3. The description doesn't add meaningful parameter detail beyond the schema; it mentions the data fields but not how state/county inputs map to results. Since the schema already documents both parameters with examples, a 3 is appropriate.

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 the monthly oil & gas production time series for a U.S. county' with specific fields (period, oil_bbl, gas_mcf, well count) and temporal scope (back to 1990). It differentiates from siblings like get_county_drilling_activity by the data domain (production vs. drilling), though it doesn't explicitly name alternatives.

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 for retrieving production data and explicitly points to list_production_states for coverage discovery. However, it doesn't provide when-to-use vs. alternatives like get_county_drilling_activity or exclude scenarios, leaving the agent to infer from the name and context.

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