search_leases

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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals a key behavior: returning all leases (capped at 50) when no filters are provided. It does not state other traits like pagination or sorting, but the cap is critical and the absence of side effects is implied by 'search'.

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 two sentences, front-loaded with the core purpose, and the additional cap note is essential. Every sentence earns its place with no redundancy or filler.

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 search tool with an output schema and fully described parameters, this description covers the necessary behavior: what it searches, the filter options, and the default fifty-record cap when no filters are supplied. The output schema presumably handles return structure, so no further detail is needed.

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 summarizes the filter dimensions (state, status, date ranges) but adds little beyond the schema, which already elaborates each parameter. It does clarify that all parameters are filters, aligning with the schema's optionality.

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 searches BLM geothermal leases with optional filters on state, status, and date ranges. This goes beyond a vague verb by specifying both the resource (BLM geothermal leases) and the search/listing nature of the operation, distinguishing it from a sibling tool like get_lease_details which likely retrieves a single lease.

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 explicitly notes that all parameters are optional and that omitting them returns all leases (capped at 50), conveying when to use the tool without needing to supply filters. It gives clear context for usage but does not explicitly contrast it with get_lease_details, leaving the distinction somewhat implicit.

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