Автозагрузка: отчёт по ID

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds no additional behavioral context beyond confirming it returns statistics. No mention of what happens if the report ID is invalid or any error conditions.

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, brief sentence. It is concise and front-loaded, but it could be expanded to include important details without becoming overly long.

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 the tool's simplicity (1 parameter, read-only, annotations present, no output schema), the minimal description is adequate but misses opportunities to clarify the nature of the statistics or the version differences. It is not incomplete but could be more informative.

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 input schema describes the 'report_id' parameter with type and constraints. The description does not elaborate on the parameter's meaning or provide any additional guidance, but the schema coverage is 100%, so the baseline score of 3 applies.

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 'Статистика по конкретной выгрузке (v3)' indicates it retrieves statistics for a specific export (v3), which aligns with the name and title. However, it does not differentiate itself from the sibling tool 'autoload_get_report_by_id_v2', and the purpose is somewhat vague without specifying the exact data returned.

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 provides no guidance on when to use this tool versus alternatives such as 'autoload_get_last_completed_report_v3' or 'autoload_get_reports_v2'. There is no mention of prerequisites, optimal context, or exclusions.

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