⚠️ Target action: manual bid

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

Discloses financial impact ('affects budget spending'), daily spending cap via limitPenny, and overwrites auto strategy. Annotations already flag destructiveHint=true, but the description adds essential monetary context beyond what annotations provide.

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?

Four concise sentences, each serving a distinct purpose: purpose, warning, exclusivity/usage, validation/rate limit. Efficient and front-loaded with the core 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?

Given no output schema, the description does not explain return values but covers prerequisites (minBidPenny), constraints (limitPenny?), and rate limit. Missing idempotency mention from schema, but overall sufficient for a mutation tool with good annotations.

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% so baseline is 3. The description adds value by cross-referencing minBidPenny from cpa_target_get_bids and clarifying actionTypeID values (1,5,7). It also reiterates bidPenny lower bound, but that's already in schema. Slight improvement.

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 states a specific verb-resource combination: 'Sets a MANUAL (fixed) target-action bid for a listing.' It clearly distinguishes from the sibling tool 'save_auto_bid' by contrasting manual vs. auto bidding.

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 ('control per-action price yourself') and when not (use save_auto_bid for delegation). Also notes mutual exclusivity with auto bid and provides a 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.