land_deed_by_uid

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It reveals the possible extra verification GET, the hard two-request limit, and the content of populated results, going well beyond a simple 'get by UID' statement.

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 with no filler. The core purpose is front-loaded, followed by parameter constraints and behavioral caveats, each earning its place.

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 single-record lookup with no output schema, the description gives enough invocation detail plus result-summary hints. It does not specify error cases or behavior when both parameters are supplied, though 'exactly one' partially addresses that.

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%, but the description compensates fully by explaining that plot_id accepts numeric or display-label forms, deed_uid accepts the original spelling, and exactly one must be supplied. This adds meaning the raw schema lacks.

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 ('Get'), a precise resource ('public land-deed record'), and the lookup key ('one deed uid'). It also mentions accepted alternative identifiers, making the tool's scope readily distinguishable from sibling lookups.

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?

Clearly instructs the agent to supply exactly one of plot_id or deed_uid, which is critical usage context given the schema marks no parameters required. However, it does not explicitly name or differentiate from the sibling land_deed_by_plot, so the alternative-selection guidance is incomplete.

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