Get Property Details

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

With no annotations provided, the description carries the transparency burden. It discloses return format ('Returns the complete record as JSON; prices are USD, areas are in square feet'), data completeness caveats ('owner info where available'), and clarifies the scope ('single property'). It does not mention id/address precedence, which is already covered in the schema.

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 description is moderately long but each sentence provides distinct value: what the tool fetches, how to look up, when to use it, return format, and what it is not. It is front-loaded with the core purpose and avoids 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?

No output schema exists, so the description effectively explains expected return content by listing structural attributes, features, tax assessments, last sale, and owner info. It also clarifies units and data availability, making the tool's behavior sufficiently predictable for an agent.

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 100%, so the parameters are well-documented in the schema. The description restates the two lookup options (id or address) but does not add extra meaning beyond what the schema already provides, such as formats or precedence details.

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 uses a specific verb and resource: 'Fetch the FULL record for a single property' and lists concrete attributes. It explicitly distinguishes from siblings by stating 'This is a property RECORD, not a for-sale/rent listing', making the tool's scope unambiguous.

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 provides clear when-to-use guidance: 'Use this after search_properties to drill into one property, or on its own when you already have the exact address.' It also warns against using it for listings, though it does not explicitly name alternative tools like get_rent_estimate or list_active_listings.

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