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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, but the description adds real behavior: default exclusion of expired/canceled/filled orders, the sort order of offers, presence of loan-collateral and 'still being added' flags plus their implication for a sale, and the minOfferUsd-style filtering concept. Remaining gaps are minor (no pagination/size limits for 'all listings').

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?

Content-dense and front-loaded: the first sentence identifies the resource and its ranked contents before any caveats. Each clause carries information, though the single long enumeration sentence is heavy to scan.

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?

With no output schema, the description correctly carries the return-value burden, covering fields, sorting, exclusions and the collateral/listing-state flags. The notable omission is identification: no parameter is required, yet the description never says whether slug or tokenId is needed to target a property.

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 coverage is 100%, so slug, tokenId, status and minOfferUsd are already documented. The description reinforces status semantics but adds nothing about minOfferUsd's USD threshold behavior or how slug vs tokenId should be chosen, so the baseline of 3 applies.

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?

States a specific verb and resource ('listings and offers on one property') and enumerates exactly what is returned: lowest active listing, all listings, offers sorted high-to-low with price, counterparty, expiry, restrictions and documents. An agent can distinguish this from siblings like get_land_property, get_land_loan or get_land_valuation without opening any schema.

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?

Usage is implied rather than stated: it hints the property page is where offers are made, and notes expired/canceled/filled orders are excluded unless status='all'. There is no explicit 'use this when X, use get_land_property when Y' routing, and nothing on the sibling tools an agent should prefer for a property summary or a single loan.

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