Target action: bids

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

Reinforces read-only nature as in annotations, adds explicit statement 'does not change spending' and rate limit. No contradictions with 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?

Five sentences, each with distinct value: purpose, safety, usage guidance, sibling differentiation, rate limit. No redundancy.

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?

Despite no output schema, description details all returned fields (price, min/max/recommended, strategy, forecast) and units (kopecks). Fully covers information needs for tool selection.

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?

Only one parameter (itemId) with full schema coverage. Description mentions 'ONE listing' but does not add semantic detail beyond the schema. Baseline 3 is appropriate.

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 specifies verb 'Returns', resource 'detailed information about current and available target-action bids', scope 'for ONE listing', and lists specific data fields. Distinguishes from sibling tool cpa_target_get_promotions_by_item_ids.

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?

Explicitly states when to use ('before save_manual_bid/save_auto_bid'), when not to use (for multiple listings), names alternatives, and provides rate limit (20 req/min).

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