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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the whole tick is never served, `field` restricts output, results include Merkle openings verifiable with hashes alone, and mapped fields may appear conditionally. It omits auth requirements, error behavior, and side-effect status, but for a query-like operation the disclosed constraints are substantial.

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 dense, run-on, cryptic paragraph that mixes input requirements, output contents, verification details, and conditional availability without clear structural separation. It is not front-loaded with a plain action statementcarrying a lot of useful detail, but it forces the agent to parse through a wall of domain jargon.

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?

The description lists the major output components and important constraints, which is valuable given there is no output schema. However, it omits precise return structure, exact units or formats for the numeric readings, error conditions, and any guidance on how the Merkle opening should be consumed. It is more complete than minimal, but not fully self-sufficient for an unfamiliar agent.

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%, yet every parameter receives meaningful context: `addr`, `start`, `amount_degrees`, and `salt` are called the lease's own fields; `tick` is the optional named tick; and `field` is explicitly narrowed to `wind_10m`, `wind_850`, and `magnet`. This fully compensates for the bare input schema.

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 eventually identifies a concrete read operation: submit lease fields, optionally name a tick and field, and receive the held address plus mapped facet observations, the tick record, census, and stamps. It is not a tautology and states a resource (the facet/ground) and a specific scope. It does not explicitly differentiate from siblings like `ground` or `quote_ground`, but the core purpose is recoverable.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternative sibling tools. The conditional notes about `field` narrowing and magnet availability are parameter-level guidance, not tool-selection guidance. An agent cannot tell why `open_ground` should be chosen over `ground`, `hold_ground`, or `quote_ground`.

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