search_offers

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

With no annotations provided, the description fully discloses behavior: return format (total, returned, offers), offer structure (id, title, price in UAH, currency, location, url), sorting behavior (price_asc/price_desc sorted client-side), filters handling (string keys or two-number arrays for ranges), and the include_promoted option. It also notes that the server accepts OLX-style wrappers for range filters.

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 concise: a one-sentence purpose and return format summary, followed by a clear paragraph of usage guidelines. Every sentence adds unique value, no repetition of schema or annotations, and the structure front-loads the essential purpose.

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 12 parameters, no output schema, and no annotations, the description is remarkably complete. It covers the return format, offer fields, parameter usage patterns (query vs filters, location/category IDs), sorting behaviors, and platform alternatives. The description fully compensates for the lack of structured annotations and output schema.

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?

While schema coverage is 100%, the description adds significant meaning beyond the schema: it explains how to use the query parameter for attributes without dedicated filters, clarifies the client-side sorting behavior for price sorts, details the filter value format (string or two-number list) and the accepted OLX wrapper, and specifies that include_promoted controls top_ad, highlighted, and urgent listings. This goes well beyond the schema's field descriptions.

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 it searches OLX.ua and returns a page of matching offers plus total count. It specifies the return format and distinguishes from sibling tools (hotline_search_offers, prom_search_offers, list_filters, etc.) by naming them explicitly, making the tool's specific function unambiguous.

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 provides explicit when-to-use guidance: call list_filters for category-specific attributes, list_regions for location IDs, list_categories for category IDs. It also tells the agent when to use alternatives (hotline_search_offers and prom_search_offers for price comparison across shops) and warns against deep pagination in favor of filters.

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