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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description usefully adds that one call returns every finding 'each with its official county, State or federal source, and a permalink to cite', which is real behavioral value beyond the annotations. It does not address failure modes (unknown TMK, ambiguous address) or rate/latency characteristics.

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 usage trigger is correctly front-loaded, but the body is a sprawling enumeration that repeats the opening framing ('Answers questions about one Hawaiʻi lot, by TMK or street address') and then lists roughly thirty attributes, many of which are edge-case or island-specific (TVR standing on Kauaʻi, lava zone on Hawaiʻi Island). It is far longer than needed to select and invoke the tool, and the keyword-stuffed list hurts scanability.

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 carries the return-value burden and does so thoroughly: every finding type, the fact that results are sourced and permalinked, and that one call covers the whole lot. Only the response shape (flat list vs. grouped sections) and error behavior remain unspecified.

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 100% and both parameters carry their own examples and formats, so the schema does the heavy lifting. The description confirms the two lookup modes exist but adds no format, precedence (what happens if both tmk and address are supplied, given neither is required), or normalization guidance beyond the 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 first sentence names a specific verb+resource ('Look up one Hawaiʻi lot by TMK or street address') and enumerates the exact facts returned, so the agent knows precisely what the tool produces. The single-lot scope is clear, which implicitly distinguishes it from the sibling search_lots, though no sibling is named.

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?

'Use this when someone asks about one Hawaiʻi lot by TMK or street address' gives an explicit trigger condition and the two acceptable identifiers. It stops short of naming alternatives (e.g. search_lots for multi-lot or unknown-parcel lookups), so routing when the parcel identifier is not yet known is left to inference.

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