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

With no annotations, the description carries the burden of behavioral disclosure. It conveys that the tool is informational and enumerates the data it exposes, but it never explicitly states that it is read-only, what the response structure looks like, or how domain terms like 'Earth ladder' and 'reserve prices in degrees' should be interpreted.

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 a single dense sentence that front-loads the core purpose and then compresses all important content categories into a readable list. There is no filler, though the heavy use of domain-specific terms makes it slightly less accessible than it could be.

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 zero-parameter tool with no output schema, the description provides the essential high-level contents: available strata, terms, reserve prices, how to bid and claim, and stated limits. It would be stronger with an explicit statement of return format and read-only behavior, but the invocation path itself is unambiguous.

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?

The input schema has zero properties, so there are no parameters to document. The description does not need to add parameter-level semantics because schema coverage is effectively complete by having no inputs.

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 opens with 'What is for lease' and enumerates the catalog's contents: strata L4-L7, terms, reserve prices, bidding/claiming instructions, and founding-period limits. This clearly marks it as an informational catalog rather than an action tool like bid or claim, though it does not use an explicit verb such as 'lists' or 'returns.'

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 phrasing 'What is for lease' implies this is the tool to consult for available lease inventory and terms before taking actions like bidding or claiming. However, it does not explicitly name sibling tools or state when not to use it, so the usage guidance remains implicit rather than declarative.

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