redfin_similar

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

Annotations are absent, so description must fully disclose behavior. It states 'Faithful pass-through of Redfin's public similars resource' implying no transformation beyond normalization, but lacks details on rate limits, auth requirements, error handling, or what happens for invalid property IDs. Minimal disclosure.

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 with no fluff. Purpose front-loaded in first sentence. Actionable and scannable.

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, but description mentions 'normalized listing rows' which provides some clue about return format. However, lacks details on fields included, number of results, or edge cases. Adequate for a simple tool 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?

Single parameter property_id with schema description 'Redfin property id'. Schema coverage is 100%, so description adds no extra meaning. Does not specify format or how to obtain the ID.

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?

Clearly states verb 'Get' and specific resource 'Redfin comparable listings'. Distinguishes from sibling tools like redfin_search and redfin_property by focusing on similar listings. Mentions output format 'normalized listing rows' and pass-through nature.

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?

No explicit guidance on when to use this tool versus alternatives such as redfin_search or redfin_property. No mention of prerequisites, context, or situations where it should not be used.

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