yandex_query_stats

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

No annotations are provided, so the description carries the burden; it does disclose the returned metrics, the date format, and the default window (last week), which is useful behavioral context. It omits that this is a read-only stats call, says nothing about the 500-row default limit's effect, rate limits, or truncation behavior.

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?

Front-loads the purpose in one sentence, then parameter notes in a compact second block. Slightly marred by doubled-backtick formatting noise, but there is no 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?

An output schema exists, so return values need not be described. Still, for a 6-parameter tool with 0% schema coverage, missing guidance on 'limit' (pagination/capping behavior) and on which Yandex data source this queries leaves gaps an agent must guess at.

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 0% and the schema declares no enums, so the description is doing real work by enumerating the valid order_by values (TOTAL_SHOWS/TOTAL_CLICKS) and the five device values, plus the YYYY-MM-DD date format and last-week default. It leaves 'site' and 'limit' unexplained, which keeps it below a 5.

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?

States a specific resource and metric set: top Yandex search queries with shows, clicks and average position. An agent can distinguish it from aggregate siblings like yandex_site_summary, though the description never explicitly contrasts the two.

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?

Usage is implied by the resource name (query-level performance reporting for a site), and the order_by/device values hint at the reporting use cases. There are no explicit when-to-use or when-not-to-use statements, and no routing away from yandex_site_summary or bing_query_stats.

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