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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds scope context (aggregate over a tokenized land-trust network) but says nothing about freshness/refresh cadence, caching, or how expensive the call is — meaningful gaps for a network-wide aggregate endpoint.

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 front-loaded sentence carries the verb, the scope, and the full metric inventory with no filler. The inline gloss on Fabrica ('where US land is held in trusts represented by tokens') is slightly explanatory overhead, but it earns its place for an agent unfamiliar with the domain.

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 does the right thing by enumerating the returned metric categories, which is the main thing an agent needs to decide whether this call answers the question. The remaining gap is the absence of any note on data staleness or call cost, but for a parameterless read-only endpoint this is close to 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?

The tool takes zero parameters, so there is nothing for the schema to document and nothing the description needs to compensate for. Baseline 4 applies; the description correctly avoids inventing filter semantics it does not support.

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 gives a specific verb and resource ('Get network-wide statistics for Fabrica') and enumerates exactly which metrics are returned (properties, value, lending volume, TVL, geography, contract addresses), so the agent knows the surface covered. It does not, however, differentiate itself from overlapping siblings such as get_fabrica_lending_market or get_fabrica_loan_book, which also return lending figures, leaving the agent to infer that this one is the broad overview.

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?

'Network-wide' implies this is the aggregate/overview entry point, which is usable context, but there is no explicit guidance on when to prefer it over the many narrower siblings (get_land_portfolio, get_fabrica_loan_book, get_land_valuation). No exclusions, prerequisites, or alternatives are named.

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