Zamień link OLX na parametry

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the endpoint is experimental and lists the output parameters, but it does not describe error behavior, validation rules, or side effects for malformed or non-OLX URLs.

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 three short sentences with no wasted wording. It front-loads the conversion purpose, then gives the example and the downstream usage note.

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 one-parameter converter with no annotations and no output schema, the description covers the essential context: accepted input forms, an example, the output fields produced, and the intended downstream tool. It is only slightly incomplete on failure modes and strict URL validation.

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 0%, so the description must clarify the single required url parameter. It does so by stating that the input may be a full OLX search URL or a path and by giving a concrete example with a query string, though it does not define accepted domains or validation details.

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 states a specific verb and resource: convert an olx.pl search URL or path into API parameters, and it enumerates the resulting fields category_id, city_id, region_id, and filters. It also distinguishes the tool from search_offers by telling the agent to use the result there.

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 gives clear usage context: use this tool when starting from an OLX search URL or path, then pass the result to search_offers. It provides a concrete example URL, but it does not explicitly state when not to use it or describe alternative paths for forming a search directly.

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