ebay_update_bid

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

The annotations provide readOnlyHint=false, so the write behavior is already indicated; the description simply repeats 'Update' without adding context about side effects, authorization needs, rate limits, or reversibility. It does not go beyond what the annotation already conveys.

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?

The description is a single short sentence with the core action front-loaded. There is no wasted text, though the brevity leaves out potentially valuable elaboration about the bid update context.

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?

The schema is rich and covers all parameters, and the annotation indicates a write operation. However, the description does not explain the relationship between adId and campaignId or the expected effect of updating the bid, and it is not sufficient to distinguish from similar bid-update tools on its own.

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?

The schema description coverage is 100% and clearly documents adId, campaignId, and request.bidPercentage, so the baseline is 3. The description adds no extra meaning beyond the schema, merely restating the operation.

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 uses the specific verb 'Update' with the resource 'bid' and identifies the eBay Marketing API, making the primary action clear. It does not explicitly differentiate from sibling tools like ebay_update_bidding_strategy or ebay_bulk_update_ads_bid_by_inventory_reference, which also involve bid-related updates.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites, whether adId/campaignId must already exist, or any exclusions for bulk or strategy-specific updates.

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