yd_metrika_report_comparison

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

No annotations provided. Description only includes 'Get' implying read-only, but lacks disclosure of return format, pagination, authorizations, or any side effects. For a report tool, expected behavioral details are missing.

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?

Single sentence of 9 words, front-loaded with key information. No redundancy, every word earns its place.

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?

No output schema exists, so description should mention what the report returns (e.g., format, structure). It does not. For a complex tool with 7 parameters and 6 required, more description of behavior or output is needed.

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 100%, so each parameter already has a description. The tool description adds the 'A vs B periods' context but does not enhance individual parameter meaning beyond what schema provides. Baseline 3 is appropriate.

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 clearly states verb 'Get' and resource 'Metrika comparison report', with explicit purpose of comparing A vs B periods. This distinguishes it from other report tools like yd_metrika_report (single period) and yd_metrika_report_by_time (time series).

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?

Description implicitly indicates usage for period comparison but does not explicitly state when to use or not use this tool, nor does it mention alternatives. No guidance on prerequisites or context.

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