Статистика звонков

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds that the response includes per-day statistics with specific categories (total/new/answered/new answered), but does not disclose potential return formats or pagination. No contradiction with annotations.

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, no wasted words. The first sentence clearly states the purpose and output, the second provides additional context on parameters. Appropriate length for the complexity.

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, so the description must explain return values. It describes the response as statistics per day with categories total/new/answered/new answered. While not highly detailed, it gives enough context for an agent to understand the output. Could specify exact structure but sufficient.

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?

All four parameters have descriptions in the schema (100% coverage). The tool description adds context that date format is YYYY-MM-DD (redundant with schema), explains the default behavior for itemIds, and notes the default for user_id. This adds value beyond the schema.

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 it provides call statistics for ads over a period, broken down by days with categories total/new/answered/new answered. However, it does not explicitly distinguish from sibling tools like calltracking_get_calls which provides individual call records, nor clarify the read-only nature despite 'post' in the name.

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 mentions that without itemIds it returns stats for all user ads, implying when to filter. But it lacks explicit guidance on when to use this tool versus sibling tools like calltracking_get_calls, and no when-not-to-use scenarios are provided.

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