searchListings

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states 'Search for listings' and lists filters, without revealing pagination behavior, response format, rate limits, or any side effects. It is not misleading but lacks essential 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 sentence, front-loaded with the core action. It is fairly concise, though slightly run-on due to the enumeration of filters and domains, which could be restructured for readability without adding length.

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 9 parameters, no output schema, and no annotations, the description is too sparse. It omits that domain is required, does not mention the valid enum values, does not address pagination limits or sorting, and gives no indication of the response structure. This leaves significant gaps for an agent to correctly use the tool.

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 description mentions query, category, location, and price range, which map partially to schema properties. However, it does not clarify that domain is required, nor does it mention pagination (page, limit) or sortBy. With 0% schema description coverage, this partial compensation is insufficient.

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 listings on specific OLX domains with filters, which is a specific verb+resource. It distinguishes itself from sibling getListingDetails by focusing on search rather than fetching details of a single listing.

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 explicit guidance on when to use this tool versus the sibling getListingDetails. The description implies general search usage but does not state when to choose this over alternatives or what scenarios it is suitable for.

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