ebay_bulk_migrate_listing

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

With no annotations provided, the description carries full burden for behavioral disclosure, but it only states 'bulk migrate'. It does not mention whether original listings are modified or deleted, if the operation is synchronous, or any error handling behavior.

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?

At six words, the description is extremely concise but omits critical information. It prioritizes brevity over clarity, resulting in under-specification.

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 annotations, no output schema, and a single undocumented parameter, the description is severely incomplete for a bulk migration operation. Users need details on prerequisites, side effects, and the structure of the request body.

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 coverage is 100% with one parameter 'body', but the description merely repeats the parameter name as 'Generated BulkMigrateListing request body', adding no semantic detail beyond the schema. The agent gains no insight into what the body should contain.

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 verb 'migrate' and specifies the resource 'listings to the inventory model', which clearly indicates the tool's action and distinguishes it from create/revise/end listing tools. However, 'migrate' could be more explicit about the conversion process.

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?

There is no guidance on when to use this tool versus alternatives like ebay_create_listing or ebay_revise_listing. No prerequisites or scenarios are described, leaving the agent to infer usage context.

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