search_listings

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

No annotations are provided, so the description carries the burden. It discloses the one-page pagination behavior and supported filters, but it does not mention result format, default city behavior, or whether filters are required. This is adequate but leaves gaps.

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, with the core action first, then the key pagination behavior, then the supported features. Every sentence contributes and there is no filler.

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?

For a tool with 10 optional parameters and no output schema, the description gives a useful overview but does not explain return shape or how city and cityId relate. It is minimally sufficient for an agent to invoke basic searches, but not fully complete.

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 80%, so baseline is 3. The description repeats the parameter capabilities (query, city, category, region, price range, sorting) without adding meaning beyond the schema; no parameter details are enriched.

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 opens with 'Search Sheypoor listings', a specific verb and resource, and immediately adds 'Returns one page of results (default 24)', which distinguishes it from the sibling search_listings_all for paginated/all-results searches.

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?

It states the tool returns one page, giving clear context that this is for single-page searches, but it does not explicitly name alternatives or say when not to use it. The sibling search_listings_all is implied but not referenced.

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