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

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

Annotations (readOnlyHint=true, destructiveHint=false) already indicate safe, read-only behavior. The description adds context by stating it returns 'просмотры, контакты' and mentions period and groupings. It does not contradict annotations and provides useful behavioral insight about shallow stats.

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?

Two sentences, front-loaded with purpose and period, then format and examples. No unnecessary words. Each sentence adds distinct value.

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?

Describes date format, grouping, fields, but does not cover the response structure (output schema missing). For a stats tool, the return format (e.g., time series, metric values) would be helpful. It is adequate but leaves gaps.

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%, so baseline is 3. Description adds value by specifying date format (YYYY-MM-DD), concrete metric examples (["uniqViews","uniqContacts","calls"]), and clarifying the fields parameter's purpose. This enhances the schema descriptions.

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 it retrieves shallow statistics (views, contacts) for ads over a period. The name 'items_post_item_stats_shallow' and title 'Статистика объявлений' align with purpose. It does not explicitly differentiate from sibling tools like items_post_calls_stats or items_post_item_analytics, but the phrase 'поверхностная' (shallow) implies a lighter scope.

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?

The description specifies required date format (YYYY-MM-DD) and grouping options (day/week/month), which informs when to use. However, it does not provide explicit guidance on when to choose this tool over alternatives (e.g., for quick overview vs. detailed analytics). Usage is implied but lacks exclusion criteria.

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