land_plot_snapshot

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses concrete behavior: each call reads afresh, issues at most four GETs, and returns a whole result only if deed identity verifies and all three follow-up reads succeed. It also states there are no account defaults, caching, or inferred data, which meaningfully shapes expectations about failure and completeness.

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?

Three dense sentences that front-load what is read, then input format, then call semantics; every clause carries information. Slightly packed with semicolon-style clauses, but nothing is redundant or padded.

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 and one parameter, the description carries the needed burden: it specifies the endpoint fan-out, the success/failure atomicity rule, and the null-project case. Return field details are left implicit, but for this composite read that is a minor gap.

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%, so the schema is just an integer-or-string anyOf with no meaning attached. The description compensates by explaining the two accepted forms: a numeric plot_id or a padded region-tract-plot label, which is the key ambiguity an agent would otherwise hit.

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?

It names a specific verb (read) and a concrete composite resource (one plot's deed, active project, stake details, stake assets) drawn from four endpoints. This clearly separates it from narrower siblings like land_deed_by_plot or land_stake_assets, which cover only one slice of the same data.

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 description tells the agent what input to supply ('numeric plot_id or padded region-tract-plot label') and notes that a null active project is a legitimate result, but it never states when to prefer this aggregate over the narrower siblings (land_deed_by_plot, land_stake_details). Usage is implied by the composite scope rather than made explicit.

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