ebay_bulk_migrate_listing

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

With no annotations, the description must disclose behavior. It only says 'migrate', implying mutation, but doesn't clarify if listings are removed, created, or what happens to existing inventory items. No side effects or success criteria are mentioned.

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 sentence, making it concise and front-loaded. However, it sacrifices detail for brevity, which may reduce usefulness for an AI agent.

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 the tool's complexity (nested objects, bulk operation, no output schema), the description is incomplete. It lacks information on prerequisites, error handling, rate limits, or the migration workflow. Sibling tools are abundant but not referenced.

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% for the outer 'requests' field, but the description adds no extra meaning. The inner 'listingId' field has no description in the schema or the tool description. The description merely repeats the schema's brief 'Bulk listing migration requests'.

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 'Bulk migrate listings to the inventory model' specifies a clear verb (migrate) and resource (listings to inventory model). It distinguishes from sibling tools like ebay_create_listing or ebay_bulk_create_offer, though the term 'inventory model' is vague.

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 provided on when to use this tool versus alternatives. There are many sibling tools for listing operations, but the description does not mention context, prerequisites, or exclusions.

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