Search Sales

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that results include price_per_unit and price_per_sqft and display on an interactive map, providing useful output context. However, it does not explicitly confirm that the operation is read-only or mention any rate limits or permissions, though this is largely implied by 'Search'.

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 three sentences, front-loads the purpose, and each sentence earns its place. It is concise, informative, and avoids unnecessary detail.

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 the core purpose, filter capabilities, return fields, and display behavior, which is strong for a search tool. However, it claims 'in NYC' while the schema also supports Philadelphia, and it does not mention the required 'city' parameter or the NYC-only 'borough' field. These gaps are partially addressed by the schema, so the overall completeness is strong but not perfect.

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 covers 100% of parameters with descriptive text, so the description adds little beyond what the schema already provides. Mentioning 'neighborhood, price range, building type' simply restates existing schema fields, and 'and more' is vague. The description does not clarify parameter syntax or add new semantics.

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 identifies the tool as a search for recent property sales in NYC, which distinguishes it from sibling tools like search_properties (broader property search) and get_sale_history (historical sales for a specific property). It also mentions filtering options and return fields, making the purpose unmistakable.

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 usage for finding recent sales with filters, but it does not explicitly state when to use this tool over alternatives such as search_comps or search_properties. No exclusions or alternative tool names are mentioned, so the guidance is only implicit.

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