ebay_get_feed_task

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

Annotations already declare readOnlyHint=true, but the description adds real context: the status lifecycle (QUEUED, IN_PROCESS, COMPLETED/COMPLETED_WITH_ERROR), that the file is ready at completion, and the OAuth scope requirements per feed type. This exceeds what annotations provide.

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?

Two sentences, purpose front-loaded, with the OAuth scope detail second. Efficient, though the parenthetical about reserved feed types is somewhat tangential to invoking the tool.

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?

With no output schema, the description helpfully enumerates the return fields and status progression, and covers the non-obvious OAuth scope dependence. An agent has enough to call it correctly, though it doesn't mention polling cadence or where to fetch the ready file.

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% and the schema already explains taskId's origin (from the Location of a create call or a task list). The description merely repeats 'by taskId' without adding format or constraint detail, so the baseline 3 applies.

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?

States a specific verb and resource - get one Feed API task by taskId - and enumerates the returned content (feed type, status, timestamps, upload summary). The singular 'one ... by taskId' clearly distinguishes it from the sibling ebay_get_feed_tasks list tool.

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?

Usage is only implied: retrieve a task's status/details after creating or listing feeds. There is no explicit when-to-use, no direction to the related siblings like ebay_get_feed_task_result_file, and no stated exclusions.

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