yd_wordstat_top_requests

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

Discloses key behaviors: last 30 days, returns phrases with counts, 1 quota unit per request. With no annotations, this provides adequate transparency for a simple read operation. Could mention error handling or further detail on output format.

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?

Two short, front-loaded sentences with no redundant information. Every sentence adds value.

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 simple tool with well-documented parameters, the description adequately covers purpose, time constraint, output, and cost. Could mention the ability to filter by region or device, but these are in schema. No output schema, but description covers the basics.

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 baseline is 3. Description does not add extra meaning beyond schema; it only restates the overall purpose but does not elaborate on parameters like num_phrases, regions, or devices.

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?

Clearly states it retrieves popular search queries for a keyword from Yandex Wordstat, with a 30-day time window. Distinguishes from siblings by specifying 'top requests' and including time constraint.

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?

Implied usage from description but no explicit guidance on when to use this tool versus siblings like yd_wordstat_dynamics or yd_wordstat_regions. No 'when not to use' or alternative mentions.

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