Target action: prices by listing

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds that it does not change spending, reinforces read-only nature, and provides additional constraints (max 200 items per request, rate limit).

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?

Description is well-structured with front-loaded purpose, followed by details, usage guidance, and rate limit. Every sentence adds value; 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, the description lists returned fields (actionTypeID, strategy, price/limit/budget). It is complete enough for a batch read tool with strong annotations. Minor gap: could mention response format (e.g., array) but not critical.

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 description coverage is 100% and the description does not add significant new meaning beyond what the schema provides for the single parameter. Mentions 'in kopecks' for prices but that applies to output, not parameter.

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 returns current target-action bids and budgets for multiple listings at once (batch up to 200). It specifies output details (actionTypeID, strategy, price/limit/budget) and distinguishes from the single-listing sibling cpa_target_get_bids.

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 says when to use (bulk-check current settings) and when not to (for a single listing with full min/max/recommendations/forecast, use cpa_target_get_bids). Also mentions rate limit of 400 requests/min.

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