⚠️ BBIP: купить продвижение

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

Beyond annotations (destructiveHint=true), the description warns that the tool is paid, debits money from balance, and explains the idempotency key behavior (cache and conflict). This adds critical financial and safety context not captured by annotations alone.

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, efficient paragraph with clear warnings and instructions. It uses bold and emojis to highlight key information, and every sentence serves a purpose.

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?

The description explains input derivation and safety features well, but it does not describe the output or return value of the tool. For a paid service, knowing the response format (e.g., order ID) would be helpful. Error handling beyond idempotency conflicts is also omitted.

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 adds meaning by linking each item sub-field to specific fields in the suggests response (e.g., budgets[].oldPrice, duration.recommended). However, the input schema already provides good descriptions for each parameter, so the added value is moderate.

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 creates a BBIP promotion order for items, explicitly marking it as paid and referencing the prerequisite suggests tool. It distinguishes itself from siblings by being the order creation endpoint, while siblings like promotion_get_bbip_suggests_by_items_v1 are for suggestions.

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 explicitly instructs to first call promotion_get_bbip_suggests_by_items_v1 and details how to map fields (oldPrice, price, duration) from the suggests response to the input. It also explains the dryRun and idempotencyKey parameters for safe testing and deduplication, providing comprehensive usage guidance.

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