yd_report

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

No annotations are provided, so the description carries the full burden. It states 'Returns TSV data' but does not explicitly confirm it is read-only, nor does it disclose any side effects, auth requirements, or rate limits. The behavioral disclosure is minimal.

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?

Extremely concise with two sentences. No unnecessary information. However, it might be too short to be fully informative, but for the purpose of conciseness, it is efficient.

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 6 parameters, no output schema, and no annotations, the description should provide more context. It only mentions 'TSV data' without explaining the return structure, what each report type does, or how field_names affect output. The description is incomplete for an agent to successfully use this tool.

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% with clear descriptions for all 6 parameters. The tool description adds no extra value beyond the schema (e.g., 'Returns TSV data' does not elaborate on parameter usage). Baseline score of 3 is appropriate given high schema coverage.

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 clearly states the verb 'Get' and resource 'campaign statistics report', which is distinct from sibling tools like yd_ads_get and yd_keywords_get. However, it could be more specific about the scope (e.g., Yandex Direct) and the fact that it returns a report with selectable fields.

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 vs alternatives like yd_ads_get. Does not specify prerequisites, exclusions, or typical use cases. The description is insufficient for an agent to decide when to invoke this tool.

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