redfin_property

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

With no annotations, the description carries full burden. It correctly implies a read operation ('get', 'returns') but lacks details on potential side effects, rate limits, or authentication requirements. The mention of 'public stingray detail API' adds some transparency but overall minimal depth.

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 two sentences, front-loading the purpose. Every sentence adds value: first states what the tool does, second explains input options. No redundant information.

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 input usage and API source, but lacks output detail. Without an output schema, agents would benefit from knowing what fields are returned (e.g., address, price, etc.). 'Normalized Redfin public property details' is vague. Adequate but incomplete.

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?

The input schema has 100% description coverage. The description adds value by explaining the relationship between parameters (url as primary, property_id with optional listing_id for completeness) and provides a usage pattern. This goes beyond the schema's individual descriptions.

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 Redfin property and returns normalized details. It mentions the primary input methods (URL or property ID), which helps understand the tool's purpose. However, it doesn't explicitly differentiate from sibling tools like redfin_search or redfin_estimate, though the specificity of 'property' is implicit.

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 explains how to invoke the tool (listing URL or property ID) but does not provide guidance on when to use this tool versus alternatives like redfin_search or redfin_similar. No 'when to use' or 'when not to use' information is given.

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