get_lease_details

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Retrieve' clearly indicates a read-only operation, which is a key behavioral trait. However, the description does not mention potential errors, authentication requirements, or the scope of 'details' beyond what the output schema likely covers. It adds some value but leaves gaps.

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 sentence that is front-loaded with the action and resource. No filler, no redundancy. Every word contributes to the purpose, making it highly concise and well-structured.

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?

This is a simple one-parameter read tool with an output schema, so the description doesn't need to explain return values. It adequately communicates the purpose and key. However, it doesn't mention any edge cases or error behavior, but for a straightforward getter, it is largely complete.

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 schema already fully defines the sole parameter with an example. The description reinforces the meaning by mentioning the case serial number in a lease context, but doesn't add significant new meaning beyond the schema. Baseline 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 a specific action ('Retrieve details') and a specific resource ('BLM geothermal lease') identified by a key ('Case Serial Number'). This directly distinguishes it from the sibling search_leases, which is a search tool, while this is a direct lookup.

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 explicit guidance is given on when to use this tool versus search_leases. The description implies that you need a serial number, but it doesn't state the alternative use case or when to prefer one tool over the other. Without this, the agent may not know that this tool is for direct retrieval and the sibling is for searching.

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