ebay_resume_promotion

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

With only readOnlyHint=false, the description adds minimal behavioral context beyond the annotations. It essentially restates the action without providing side effects, idempotence, auth requirements, or preconditions. There is no contradiction with annotations, but also no added transparency.

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?

A single terse sentence with no filler, front-loading the action. It is appropriately concise for simple operation, though it sacrifices valuable usage guidance for brevity.

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?

For a one-parameter mutation without an output schema, the basic mechanically necessary information is present. Missing are when-to-use context against sibling promotion/campaign tools and expected outcome, leaving it minimally viable but incomplete in guidance.

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 input schema covers the single required parameter with a description ('promotionId required endpoint parameter'), so the schema carries 100% of the load. The description itself adds no extra meaning, giving the baseline score of 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?

The description uses a specific verb 'Resume' targeting the 'promotion' resource, which is clear and distinct from sibling tools like ebay_get_promotions or ebay_delete_item_promotion. It does not explicitly differentiate itself from ebay_pause_promotion, but the action and resource are unambiguous.

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 no guidance on when to use this tool versus alternatives such as ebay_pause_promotion, nor does it mention any prerequisite like the promotion needing to be in a paused state. Context signals also don't provide this information.

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