ozon_ad_statistics_daily

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

With no annotations, the description must carry the full burden of behavioral disclosure, but it only says 'daily ad statistics.' It does not explain whether this is a read-only operation, how date bounds are handled, what grouping/period behavior occurs, or what the returned data looks like.

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 short and the key phrase is front-loaded, but the parenthetical Russian translation 'ежедневная статистика' is redundant and adds no value. The brevity is more under-specification than effective conciseness.

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 three required parameters, no annotations, no output schema, and a cluttered sibling space, the description is far too thin. It does not explain campaign selection, date formats, daily aggregation details, or how this tool differs from nearby statistics tools.

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%, and the description adds no parameter information at all. The agent is left without any explanation of what 'campaigns' contains, what format date_from/date_to use, or what date range semantics apply.

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 ('ad statistics') and the daily granularity, so the basic purpose is understandable. However, it is a noun phrase with no verb, and it does not clarify what metrics or aggregation are included, nor does it distinguish itself from sibling tools like ozon_ad_statistics, ozon_ad_statistics_expenses, or ozon_ad_statistics_products.

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 is provided about when to use this tool instead of the many other ad-statistics tools. There are no stated preconditions, no mention of date constraints, and no alternatives named.

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