Szukaj ogłoszeń OLX

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

No annotations exist, so the description carries the full burden, and it discloses meaningful behavior: it is a public JSON API, returns compact offers plus total count and nextOffset for pagination. It omits auth requirements and rate limits, which is a minor gap for a read-only search tool.

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?

Three compact sentences, zero waste. The core action is front-loaded, with the ID precondition and return shape following in logical order.

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 14-parameter search tool with no output schema, the description covers the essentials: API nature, ID requirements, and return shape including total count and nextOffset. It is nearly complete, with only filter-specific semantics and rate/auth context left implicit.

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?

With 21% schema coverage across 14 parameters, the description must compensate, and it does add key meaning: location/category params require numeric IDs resolvable via resolve_olx_url, and nextOffset maps to offset. However, it leaves many filters (priceFrom/priceTo, ownerType, skipPromoted, distanceKm) unexplained beyond the schema, so compensation is only partial.

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?

States a specific verb and resource: "Search OLX offers via the public JSON API." This clearly differentiates it from the sibling get_offer (single fetch) and resolve_olx_url (ID resolution). It is clear without explicitly naming what it is not.

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?

Explicitly routes the agent to resolve_olx_url when only names are known, stating the numeric-ID precondition. This is strong alternative-routing guidance. It does not name exclusions such as when to prefer get_offer, but the context is clear enough.

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