yandex_wordstat_dynamics

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It offers only two hints: UTC dates are required and some 'server budget gate' exists, but it never explains what the budget gate does, whether the operation is read-only, or any consequences of hitting the gate. This is insufficient for a tool with no other behavioral metadata.

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 a single, efficient sentence with no filler. It front-loads the core action ('Get Wordstat demand over time') and adds date details, but the undefined 'server budget gate' is a minor structural flaw that could confuse rather than inform.

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 tool with six parameters, three required ones, and no annotations, this description is incomplete. It omits any mention of the required phrase parameter, the meaning of period, filtering options (devices, regions), or the behavior of the budget gate. Even though an output schema exists, the agent still lacks enough context to call the tool correctly.

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 description coverage is 0%, so the description should compensate by explaining the parameters. It only illuminates the date format (UTC, YYYY-MM-DD) for from_date/to_date, while phrase, period, devices, and regions remain unexplained. The description adds minimal semantic value beyond the schema's raw field names.

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 and resource – 'Get Wordstat demand over time' – which clearly distinguishes this from sibling tools like yandex_wordstat_get_top or yandex_wordstat_regions by emphasizing the temporal dimension. However, the phrase 'server budget gate' is cryptic and slightly muddies the otherwise clear purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention the sibling wordstat tools or any conditions that would select this one, leaving the agent to infer usage solely from the name and the phrase 'over time'.

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