Автозагрузка: объявления выгрузки

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

Annotations already declare readOnly, destructiveFalse, idempotent, openWorld. The description adds that the tool supports pagination and filters, which is consistent with annotations and provides additional behavioral context beyond the structured metadata.

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 sentence that is concise and front-loaded with the core purpose. Every word is informative; no fluff.

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 5 parameters and no output schema, the description covers the main purpose but lacks details about the sections filter and specific report context. Annotations compensate partially, but the description could include more context for complete understanding.

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 mentions pagination and filters indirectly but does not explain individual parameters (report_id, per_page, page, query, sections) beyond what is in the schema. With 60% schema coverage, the description adds minimal value for parameter understanding.

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 retrieves all ads from a specific report with pagination and filters. It identifies the specific resource (report items) and action (get), distinguishing it from siblings like autoload_get_report_by_id_v2 (report details) and autoload_get_report_items_fees_by_id (fees).

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 implies usage context (when you need report items) but does not explicitly state when to use this tool vs alternatives like autoload_get_report_items_fees_by_id. No exclusions or when-not to use are provided.

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