Search Booli for-sale listings

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool is read-only, paginated (via page param, check total_count/pages), and only returns active listings. This extra context about pagination behavior and listing status goes beyond what annotations provide, though it doesn't elaborate on rate limits or data freshness.

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?

Two sentences, no wasted words. First sentence conveys purpose and key scope/filter options; second covers pagination and read-only nature. Information is front-loaded and efficient.

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?

Given 20 parameters and no output schema, the description adequately covers input usage and pagination hints (total_count/pages). However, it does not describe the output structure (e.g., each listing includes id, address, etc.), leaving a gap for an agent. Annotations (openWorldHint) partially compensate, but more detail on return format would improve completeness.

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 80% (16 of 20 parameters have descriptions). The description summarizes filter categories (price, rooms, living area, etc.) but adds no detailed semantics beyond what the schema already provides. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 'active for-sale property listings' on booli.se, specifying the verb 'search' and resource 'listings'. It distinguishes from siblings like booli_search_sold (sold listings) and booli_get_listing (single listing) by focusing on active for-sale properties and referencing booli_search_areas for area IDs.

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?

Basic usage is provided: scope by area_id or location, filter by various criteria, and pagination. However, no explicit guidance on when to use this tool versus siblings (e.g., sold listings via booli_search_sold) or when not to use it. The description is functional but lacks comparative context.

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