ym_stat_data

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds limited value beyond indicating it's a GET request and that ids/metrics are comma-separated. No additional behavioral traits (e.g., rate limits, data scope) are disclosed.

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 extremely concise: two sentences plus an example with no verbosity. Every piece of information is useful and front-loaded, making it easy to parse.

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 the presence of an output schema, the lack of return value explanation is acceptable. However, the description omits behavior for pagination (limit, offset), filtering, and sorting, which are essential for a table report tool with 10 parameters.

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?

With 0% schema coverage, the description must compensate but only explains formats for ids and metrics and provides an example with date1/date2 using special values. Parameters like sort, limit, offset, preset, filters, and dimensions are not explained, leaving significant gaps.

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?

Description identifies the tool as a table report from a specific endpoint (GET /stat/v1/data) and provides an example. However, it does not explicitly differentiate from sibling tools like ym_stat_data_bytime or ym_search, which serve related but distinct purposes.

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?

No guidance on when to use this tool versus alternatives. The example implies usage for retrieving statistical data, but there is no mention of exclusions or context where other tools might be more appropriate, such as ym_search for different data access patterns.

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