ebay_create_feed_task

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

With only readOnlyHint=false as an annotation, the description carries the behavioral burden well. It discloses that eBay answers 202, that the response includes taskId and Location, the OAuth scope dependency, optional header behavior, and reserved feed types.

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 dense and front-loaded: purpose and examples come first, followed by response behavior, workflow, optional headers, and OAuth scopes. Every sentence adds relevant information, though the single long paragraph could be slightly more scannable.

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 complex mutation tool with nested parameters and no output schema, the description is complete. It explains the create-task workflow, dependent tools, return identifiers, header behavior, and authorization requirements, leaving no major gap for an agent invoking the tool.

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 already 100%, so the baseline is 3. The description adds useful feedType-specific semantics such as OAuth scope mapping and reserved feed types, and reiterates header mappings for marketplaceId and acceptLanguage, going beyond the structured schema.

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 states a specific verb (create), resource (Feed API upload/download task), and scope (without filter criteria, requiring feedType and schemaVersion). It gives concrete examples such as LMS_ADD_FIXED_PRICE_ITEM, LMS_ORDER_ACK, and Seller Hub feeds, making it easy to distinguish from sibling task tools like ebay_create_report_task or ebay_create_inventory_task.

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?

It explicitly describes the workflow: create the task, send the file with ebay_upload_feed_task_file for upload feed types, then poll ebay_get_feed_task. It also names the required OAuth scope per feed type and clarifies that certain feed types are reserved by eBay.

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