Аналитика объявлений

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

Annotations confirm read-only and idempotent behavior. Description adds the limit constraint (≤1000) and mentions support for filters and grouping. However, it does not disclose pagination behavior or response format beyond what annotations indicate.

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?

Description is concise with two sentences, front-loading the core purpose and then adding support details. No redundant information; efficient for quick understanding.

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?

Description covers main features but omits details like pagination via offset, user_id default, and grouping options (day/week/month). Given the complex nested schema, more contextual pointers would help, but the schema itself provides full parameter descriptions.

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 baseline is 3. Description provides a high-level summary of metrics, grouping, and filters, but adds no new details beyond the schema's parameter descriptions. It does not clarify enum values or default behaviors.

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 the tool provides extended analytics for ads with metrics like views and contacts, plus grouping and sorting. It differentiates from siblings like items_post_item_stats_shallow by being 'extended', but does not explicitly name alternatives.

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 implies usage for aggregated analytics with filtering and sorting, but does not specify when to choose this over similar tools like shallow stats or calls stats. No when-not-to-use guidance is provided.

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