search_recent_sales

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

No annotations are provided, so the description bears full responsibility. It does disclose some behavioral constraints (radius max 100, limit 1-500, default 20) and parameter formats, but omits important context like whether it's read-only, how 'recent' is defined, or what the default date range is.

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 front-loaded with a clear purpose sentence followed by a parameter list. While lengthy, each parameter line earns its place by adding meaning. No filler or 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?

The tool is complex with 13 optional parameters, and the description doesn't explain how parameters combine (e.g., zipCode vs address vs lat/long) or what the output looks like. The presence of an output schema mitigates the return-value gap, but combination rules are still missing.

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 description provides a clear, one-line explanation for every parameter, significantly enriching the bare schema which has 0% description coverage. It adds practical details like 'saleDateRange' format and 'radius' limits, giving the agent actionable guidance.

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 a specific verb and resource: 'Search recently sold properties (comparable sales) for pricing evaluation.' This distinguishes it from siblings like search_sale_listings (which likely targets active listings) by emphasizing sold properties.

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 gives context ('for pricing evaluation') but lacks explicit exclusions or comparisons to comparable sibling tools. It does not state when to prefer this tool over search_sale_listings or get_property_record, leaving the decision ambiguous.

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