lease_edge

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

With no annotations, the description must disclose behavioral traits but only mentions data source and content. Does not explain read-only nature, pagination, default behavior, or limitations. For example, the output schema exists but behavior around filtering by status or area is unclear.

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?

Single sentence, concise and front-loaded with the key purpose. Could be slightly more structured but no unnecessary words.

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?

Given the presence of an output schema and optional parameters, the description lacks sufficient detail for an agent to understand filtering, return format, or how to interpret results (e.g., block status). Missing parameter guidance reduces completeness.

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%, and the description provides no explanation of the three parameters (status, area, limit). Their defaults and possible values are left entirely to the schema, which lacks enum constraints or descriptions.

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?

Description clearly states the tool provides Gulf of Mexico oil & gas lease intelligence from BOEM, mentioning 218k+ leases, block status, and upcoming BBG2 auction. It distinguishes from siblings as the only lease-specific tool among many, though it lacks an explicit verb like 'retrieve' or 'search'.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, typical use cases, or contrast with sibling tools like 'energy_markets' or 'grid_intelligence'.

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