Target action: prices by listing

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

Description states 'Read-only — does not change spending' which aligns with annotations (readOnlyHint: true). It adds batch limit of 200 items per request, which is not in annotations. No contradictions; adds useful behavioral 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 concise sentences: first explains what it does and returns, second provides usage guidance and sibling reference. No redundant or extraneous content. Efficient and well-structured.

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 the single parameter and no output schema, the description adequately covers return details (actionTypeID, strategy, price/limit/budget) and batch capability. It includes rate limit and sibling distinction. Minor omission: no mention of error handling for invalid items, but acceptable for a bulk read operation.

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 coverage is 100% with a clear description of itemIDs. The description adds the batch limit of up to 200 items, which is not in schema constraints, and clarifies it's for multiple listings. This adds meaningful context beyond the schema.

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 returns target-action bids and budgets for multiple listings in batch, specifying verb 'returns' and resource 'bids and budgets'. It distinguishes from sibling tool cpa_target_get_bids by noting this is for bulk check vs single listing with forecast.

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 explicitly says 'Use it to bulk-check current settings' and provides direct alternative: 'for a single listing with full min/max/recommendations and a forecast, use cpa_target_get_bids'. Also includes a 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.