run_olx_offers_search

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 does add one genuinely useful behavioral fact the schema does not carry: billing at 1 point per returned record. However it says nothing about pagination limits behavior, auth/marketplace requirements, or what the response looks like.

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 short clauses, front-loaded with the verb and resource, then the billing note. Nothing is redundant. It is not a 5 because the facet enumeration is somewhat boilerplate list-building rather than prioritizing what an agent most needs.

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 16-parameter tool with no annotations and no output schema, the description is thin. It does not explain that all parameters are optional, how IDs like city_id/category_id are sourced (run_olx_categories, run_olx_regions), or pagination behavior, leaving real gaps for an agent to fill.

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 100%, so every parameter is already documented with enums and ranges, which sets the baseline at 3. The description's facet list (category, price, condition, seller type, location, delivery, sort) mirrors parameters without adding syntax, formats, or cross-parameter constraints.

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 gives a specific verb+resource ('Search live OLX ads') plus the facet dimensions it covers (category, price, condition, seller type, location, delivery, sort). This is more than a restatement of the name. It falls short of a 5 only because it doesn't differentiate from the closely named sibling run_olx_offers.

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?

Usage is implied by 'Search ... by keyword' and the cost note ('1 point per returned record') hints at a metered operation, but there is no explicit when/when-not guidance and no routing to alternatives such as run_olx_offers, run_olx_users_offers, or the category/region lookup tools an agent would need to obtain IDs.

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