lookup_property

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

The description adds the credit cost (2 credits) and details about return fields (roof age derivation, owner-occupancy) beyond the readOnlyHint annotation. No contradictions.

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?

One concise sentence that front-loads the purpose and key details with no redundancy.

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?

The description covers purpose, input options, key return fields, and credit cost. Minor omission: it could clarify that lat and lng are required together as coordinates.

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 coverage is 0%, and the description adds that the four parameters are alternate identifiers (address, lat/lng, parcel_id). However, it doesn't specify that lat and lng must be used together or address format, leaving semantic gaps.

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 retrieves a full property record for a single address, coordinates, or parcel ID. It lists specific data fields and distinguishes from sibling tools in other domains.

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 implies when to use (property lookup by identifier) but does not explicitly state when not to use or name alternatives. However, sibling tools are clearly different domains, so context is clear.

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