search_listings

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

No annotations are provided, so the description carries the full burden. It only states the tool searches and lists filters but does not disclose read-only behavior, authentication requirements, rate limits, or side effects. The schema provides defaults and max results but the description adds no behavioral context.

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 a single 12-word sentence that front-loads the action. While very concise, it omits details that could be added without much verbosity. No wasted words, but could be slightly expanded for completeness.

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?

Despite having 8 parameters and no output schema, the description only mentions a few filter options and fails to describe the return format, pagination, or default behavior. The schema covers parameter details, but the description lacks sufficient context about the tool's overall function and output.

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 88%, so most parameters have descriptions. The description loosely lists 'province, type, price, and more' but adds no new meaning beyond what the schema already provides. Baseline of 3 is appropriate as the description does not significantly enhance understanding.

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 listings by province, type, price, and more, specifying the resource (verified Philippine real estate listings on lupaph.com). It distinguishes from sibling tools like calculate_transfer_cost, get_legal_info, and search_guides which have different scopes.

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 guidance is provided on when to use this tool versus alternatives such as get_listing for a single listing or get_province_listings_summary for aggregated data. The description does not mention any exclusions or prerequisites.

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