search_estate_sales

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

No annotations are provided, so the description carries full behavioral disclosure. It explains the tool searches for upcoming and active estate sales and returns specific fields. The mention of EstateSales.net as the source adds transparency. However, details about pagination, rate limits, or result ordering are omitted.

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 long, with no redundant information. It is front-loaded with the primary action and purpose, and each sentence adds meaningful context.

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 mentions the key result fields (dates, addresses, descriptions, photos) and the source (EstateSales.net), which is sufficient for a search tool without an output schema. However, it could mention that at least one of zip or city+state should be provided, and it lacks details on sorting or result limitations.

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 schema covers all four parameters with descriptions (100% coverage), so the baseline is 3. The description adds value by indicating that search is by ZIP code or city/state, clarifying the relationship between parameters. But it does not provide additional syntax or usage nuances beyond the schema.

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 for estate sales by ZIP code or city/state, and specifies the kind of information returned (dates, addresses, descriptions, photos). This distinguishes it from sibling tools like estate_sale_details, which likely gets details for a specific sale, and other domain-specific search tools.

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 estate sales by location but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention scenarios where it should not be used. No exclusions or alternative tool names are given.

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