E'lonlardagi aloqa raqamlari

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds valuable behavioral details: exact return fields, hidden-phone behavior (phones [] and phone_available=false), the fact that each reveal counts in seller statistics, and the OLX 429 daily limit. This is an excellent disclosure of side effects and constraints.

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 compact, front-loaded with the core behavior, and every sentence earns its place. It packs return fields, edge cases, authentication needs, and rate-limit guidance without unnecessary filler.

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?

Despite lacking an output schema, the description covers the return shape, hidden-phone case, auth requirements, rate limits, and where to get inputs. This is complete enough for an agent to invoke the tool correctly and interpret results.

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?

The schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds useful meaning by telling the agent where offer_ids come from and reinforcing the practical limits, which goes beyond pure schema documentation.

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 ('Reveal') and resource ('contact phone numbers of one or more OLX listings') and clearly differentiates the tool from siblings by explaining it provides phone data from the 'show phone' button and listing text. This is precise and distinguishes it from likely-confused tools like olx_get_offer or olx_get_seller.

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: no login is needed, offer IDs come from olx_search_offers / olx_get_seller, and users should request only what they need due to the daily limit. It does not explicitly contrast with alternative tools, so it falls just short of full alternative-based guidance.

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