getTotalCommissionByPeriod

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. It doesn't mention pagination behavior (despite limit/rrdid parameters), response format, authorization needs, or any side effects. The one-line phrase leaves the agent uninformed about how the tool executes.

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 phrase with no filler, but it's under-specified – it reads like a title rather than a functional description. It's appropriately short but lacks structure that would help an agent parse key information.

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 4 parameters, no output schema, and no annotations, the description is too sparse to be complete. It doesn't explain what the response contains, how pagination works, or what the calculation includes beyond the bare concept. This is a significant gap for a non-trivial reporting tool.

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 the schema already documents all four parameters. The description adds no additional meaning about how parameters relate to the calculation behavior, but the schema is sufficient on its own.

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 the tool calculates deductions (commissions) for WB plus VAT over a period, using a specific verb ('Подсчёт') and resource. It conveys the core function and differentiates from generic report tools like getReportDetailByPeriod, though it doesn't name alternatives explicitly.

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 on when to use this tool versus siblings such as calculateReportMetrics or getReportDetailByPeriod. The description merely states what it does without indicating selection criteria or prerequisites.

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