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

With no annotations provided, the description carries the full behavioral burden. It discloses the time window and geographic scope, but does not mention sort order, permit status, pagination behavior, limits, or what fields each permit record will contain. This is adequate for a simple read-style listing tool but leaves room for ambiguity.

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?

One efficient sentence that front-loads the core action, resource, location, and time range. There is no filler or repetition of schema fields.

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 two-parameter query tool with an enum-based required parameter and no nested objects, the description covers the essential invocation context: what is fetched, where, and for what time period. The main missing piece is output shape or default behavior, but the schema already provides defaults and constraints for limit.

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 explains the state scope ('Texas or Oklahoma') and adds the 24-month recency window, but it does not describe the 'limit' parameter's meaning or how it controls result size beyond what the schema already implies via its default and min/max.

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 and resource: gets oil & gas drilling permits, scoped to Texas or Oklahoma with a 24-month window. This clearly differentiates it from sibling tools like get_operator_permits (operator-scoped) and get_county_drilling_activity (county-scoped).

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 clear context: use this tool when the need is recent, state-level permit filings in TX/OK. It does not explicitly state when not to use it or name alternatives, but the scope is clear enough to route the agent correctly in most cases.

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