calculateReportMetrics

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

With no annotations, the description carries the full burden. It only says 'calculates metrics', which implies a read-only operation, but it does not disclose what the output looks like, whether there are any side effects, or any constraints. This is insufficient for a tool with no other behavioral context.

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 a single concise sentence, which is structurally fine. However, it is under-informative; it does not earn its place by conveying substantial meaning, but it is not overly verbose either.

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 no output schema, no annotations, and only a vague one-sentence description, the tool is not adequately described. The agent lacks information about return values, usage context, and behavior, making the description incomplete for reliable invocation.

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?

The description does not mention any parameters, and the schema description coverage is only 50% (limit and rrdid are undocumented). The tool adds no meaning beyond the schema, leaving the agent unsure about the purpose of limit and rrdid.

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 states a specific verb ('calculates') and resource ('report metrics'), so it has some clarity. However, 'основные метрики' (main metrics) is vague and does not specify which metrics, nor does it distinguish from sibling tools like getTotalCommissionByPeriod or getReportDetailByPeriod.

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 given for when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to guess when this is the appropriate choice.

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