CPA auction: my bids

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

Description adds context beyond annotations: confirms read-only nature (does not change spending), explains pagination cursor behavior, and specifies 200 requests/min limit. No contradictions.

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?

Three sentences with no redundancy. Each sentence adds value: purpose, return fields, pagination, rate limit. Front-loaded with key action.

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 lists returned fields (pricePenny, expirationTime, availablePrices) and covers pagination and rate limits. Fully sufficient for correct invocation.

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?

Input schema covers both parameters fully. Description adds meaningful context on pagination (fromItemID as cursor) and batch size default/range, slightly elevating beyond baseline 3.

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?

Explicitly states it reads active/available CPA auction bids for user's listings. Clearly distinguishes from sibling cpa_auction_save_item_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?

Provides when to use (to read bids) and when not (to change bids, use sibling). Includes pagination details and rate limit, guiding correct usage.

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