wordstat.dynamics

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no read-only/mutation indication, no rate limits, no note that 'params' can override the payload, no statement of what the response contains. For a tool with a nested advanced override object, this is a significant gap.

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?

It is a single short sentence with no filler, which is structurally clean, but it is under-specified rather than tight: brevity here comes at the cost of information the agent needs.

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?

With 7 parameters (2 required), a nested 'params' object, no output schema, and no annotations, the definition should explain the period mapping, date format constraints, and the raw-payload override. None of that appears, so the description is inadequate for the tool's complexity.

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 57%, and the description adds essentially nothing beyond the word 'period'; phrase, devices, and regions have no schema descriptions and no compensating text. The description does not explain the distinction between period values, the from_date/to_date semantics, or the advanced 'params' escape hatch.

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 names the resource (Wordstat frequency dynamics) and the dimension it varies over (period), which does distinguish it from wordstat.top_requests, wordstat.regions, and wordstat.user_info. However, the verb is implicit and the parenthetical largely restates the tool name, so the agent gets a topic rather than a crisp statement of what the call returns.

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?

There is no guidance on when to choose this tool over its Wordstat siblings, nor any prerequisite or exclusion. The description only says what the data is, leaving the selection decision entirely to inference.

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