Booli sold-price market statistics

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

Annotations indicate readOnlyHint and openWorldHint are true; description confirms 'Read-only' and warns about thin medians via sample_size. It also clarifies it aggregates over one page, a key behavioral trait. No contradiction with annotations.

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, front-loading the purpose and immediately providing scope and usage context. Every sentence adds value without 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?

Given 22 parameters, no required ones, and no output schema, the description provides adequate context for an agent to use the tool, referencing a sibling tool for filter details and suggesting sample_size checks. However, it lacks details on response structure or pagination behavior.

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 description coverage is high (82%), so baseline is 3. The description does not add additional parameter semantics beyond referencing that filters match booli_search_sold. No new meaning beyond 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 aggregates sold-price statistics (median/average price, price per m², over/under-asking %) for an area. It distinguishes itself from sibling tool booli_search_sold by specifying it operates over one page of sold results.

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 explicitly says it uses the same scope and filters as booli_search_sold, guiding when to use it over individual listings. It also provides a caveat to check sample_size, but does not exhaustively list when not to use it.

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