lookup_parcel

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

No annotations are provided, so the description carries the full burden. It states it is a query (read operation) but does not disclose authentication needs, rate limits, what happens if both or neither parameter is given, or any side effects. Minimal behavioral context.

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?

Two sentences; the first is clear and functional. The second is promotional ('The killer query...') which adds some context but is not essential. It is reasonably concise but could be more focused on parameter guidance.

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?

Given the existence of sibling tools like get_zone_info and get_overlays_for_apn, the description does not explain how this tool aggregates data or how it relates to those. Also, with both parameters optional, the usage context is unclear. The output schema exists, so return values are covered, but overall completeness is low.

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%, yet the description only says 'by street address OR APN' without explaining formats, constraints, or that exactly one should be provided. Both parameters are optional with null default, which is confusing. The description adds little over the schema structure.

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 clearly states the tool looks up a parcel by address or APN and lists returned data (zoning, overlays, etc.). However, it does not differentiate from sibling tools like get_zone_info or get_overlays_for_apn, which may cover subsets of the 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 does not specify when to use this tool versus alternatives. It mentions 'most public sources require visiting 4+ websites' as a rationale, but lacks explicit when-to-use or when-not-to-use guidance.

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