roasr_yandex_search_queries

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

With no annotations provided, the description carries the full burden. It discloses that the tool is read-only, lists the data fields returned, and warns of an error for non-Yandex accounts. These are meaningful behavioral traits beyond the schema, though it does not mention pagination or rate limits.

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 sentences: purpose, use case, and error condition. It is front-loaded with 'Yandex Direct only, read-only' and every sentence contributes essential information without waste.

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 no output schema, the description adequately lists return fields and provides a business context. It also notes an error condition. However, it lacks mention of pagination, limits, or how results are ordered, which keeps it from a perfect score.

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 coverage is 100%, so all five parameters have descriptions. The tool description adds little beyond reiterating the date-window concept (since/until/sinceDays). Per guidelines, baseline is 3 when schema does the heavy lifting, and this is exactly the case.

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 the tool retrieves search queries for a date window, listing specific fields (query text, campaign/ad group, match type, impressions, clicks, spend, conversions). It distinguishes itself with 'Yandex Direct only' and 'read-only', setting it apart from sibling tools like yandex_breakdown or yandex_ads.

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?

It provides a concrete use case: 'use it to find what share of spend went to queries with zero conversions.' It also notes an error condition (non-Yandex account), implying when to use via platform constraint. However, it does not explicitly name alternative tools or say when not to use it.

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