Search listings

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds that it returns a compact summary with pagination meta and category aggregations, and that `raw: true` gives full payload. No contradiction.

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?

Four sentences, each serving a purpose: purpose, public access + filter combination, return structure, advanced options. No wasted words. Front-loaded with 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?

With 14 parameters, no output schema, and nested objects in extra_params, the description covers core functionality and return structure (compact summary, pagination meta, category aggregations). It does not explain all parameter details but provides sufficient context for agent use.

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 has 14 parameters with 57% description coverage. Description groups filters (category, brand, city, price range, condition, recency) and explicitly mentions `q`, `raw`, and `extra_params`. It adds context beyond the schema but does not detail every parameter (e.g., page, per_page, sort).

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 'Full-text search across OLX listings (GET /search)' and lists supported filters (category, brand, city, price range, condition, recency). It distinguishes itself from sibling tools by being the only search tool, while siblings focus on individual listings, categories, etc.

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 states 'Public — works without credentials' and describes how to combine query with filters. Mentions `raw` and `extra_params` for advanced use. Lacks explicit 'when not to use' or comparisons to alternatives, but context with sibling tools implies usage.

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