Search Properties

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

With no annotations, the description must disclose behavior, but it includes filter capabilities (lat/long, radius, square footage) that do not exist in the input schema. This is misleading about the tool's actual behavior. It does mention the summarized output and units, but the inaccuracies significantly reduce transparency.

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 concise and front-loaded with the main purpose. However, it includes extraneous details about non-existent filters, which adds confusion rather than value. It could be shorter and more accurate.

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 is incomplete because it omits how filters combine and misleadingly includes unsupported filters. It also does not explain that address overrides area filters in the main text (only in the schema). For a tool with 8 parameters and no output schema, the description should be more precise and cover actual invocation constraints.

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% and the schema already documents value formats for bedrooms and bathrooms. The description repeats that information and adds irrelevant parameters (lat/long, squareFootage) that are not in the schema, which can confuse an agent into using unsupported arguments. No meaningful added semantics for the actual parameters.

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 searches RentCast's property records database and explicitly distinguishes it from active listings by instructing to use list_active_listings instead. The verb 'Search' plus the resource 'property records database' makes the purpose specific and 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 explicit guidance on when to use this tool versus list_active_listings, and advises using the returned id or address with get_property_details for full attributes. This directly addresses alternatives and complements sibling tools effectively.

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