ebay_bulk_update_ads_status

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

The description lacks details about behavioral traits such as whether the update is destructive (archiving ads), rate limits, error handling, or if partial failures occur. With no annotations, the description carries the full burden but only says 'Update status for multiple ads', which is insufficient for a mutation tool.

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 extremely concise with two sentences, front-loading the purpose. No unnecessary words or repetition. It earns its place.

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 description is minimal and lacks context about the tool's return value (no output schema), batch size limits, asynchronous behavior, or error handling. For a bulk update tool with a nested schema, the description should provide more operational context.

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 the parameters are already well-documented. The description adds no extra meaning beyond the schema, such as the format of adId or the meaning of each adStatus value. Baseline 3 is appropriate.

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 verb 'Update', the resource 'status for multiple ads', and adds a specific constraint: 'CPC priority strategy campaigns only'. This helps distinguish it from similar tools like ebay_bulk_update_ads_status_by_listing_id, though the sibling differentiation is implicit via the name and schema.

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?

The description provides a usage constraint ('CPC priority strategy campaigns only') but does not explicitly state when to use this tool vs alternatives (e.g., ebay_bulk_update_ads_status_by_listing_id) or mention prerequisites like needing campaignId and adIds. No annotations provide additional guidance.

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