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

With no annotations, the description carries the full burden. It is transparent about the returned data categories and time windows den, and the word 'Get' signals a read-only operation. However, it does not disclose the response shape, data freshness, or behavior for an invalid or unknown slug.

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, well-structured sentence that front-loads the verb and resource and packs the specific time-window dimensions into a compact list. Every word earns its place, with no filler or repetition.

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 one-parameter aggregate query with no output schema, this description sufficiently enumerates the data dimensions and signals a consolidated response. It lacks details on response formatting or error cases, but these are minor given the tool's simplicity.

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?

There is only one parameter, `slug`, and the schema provides its type and pattern but no description. The phrase 'operator's' adds some meaning by implying the slug identifies an operator, but with 0% schema description coverage, a more explicit statement about what slug values are valid would be beneficial. The single required parameter makes this low-risk.

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 ('Get'), a clear resource ('operator's consolidated recent drilling activity'), and enumerates the exact metrics included (24mo permits, 90d spuds, 6mo new producers, current DUC inventory). It is clearly distinguishable from siblings like get_operator_permits or get_duc_inventory because it explicitly combines them into one response.

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 phrase 'consolidated ... in one response' implies the tool is for when multiple activity metrics are needed at once, but it does not explicitly name alternatives or state when not to use it. Sibling tool names suggest the split alternatives, but the description itself leaves that inference to the agent.

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