BBIP: прогноз эффекта

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

Annotations already indicate read-only, non-destructive, idempotent behavior. Description adds that forecast outputs views and contacts, and specifies units for oldPrice/price (copecks/day) and duration (days), providing useful context beyond 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: first sets purpose, second gives parameter instructions. No redundant information, efficient and front-loaded.

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?

Description covers purpose and input sources, and hints at output (views, contacts). Schema handles max items (100). Could explicitly mention max items, but overall adequate for a forecast tool with no output schema.

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 provides 100% coverage with descriptions for all parameters. Description adds cross-reference to suggests tool for obtaining values, which is helpful context. It partially repeats schema units but adds value by indicating the data source.

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?

Description clearly states it forecasts promotion effect (views, contacts) for a list of ads. It distinguishes from sibling tools by specifying input values come from suggests tool, and it is a forecast before creation.

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?

Description instructs to use values from promotion_get_bbip_suggests_by_items_v1, implying this tool is used after suggests and before create. However, it does not explicitly state when not to use it or name alternatives beyond the suggests tool.

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