ebay_get_report_tasks

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

The annotation readOnlyHint=true already signals this is a read-only operation, and the description's 'Get' aligns with that. However, the description adds no additional behavioral context, such as pagination behavior, default limits, or that it returns a list. With annotations covering the safety profile, the bar is lower, but still no extra value is added.

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, focused sentence with no filler or redundancy. It front-loads the core action and resource. It is appropriately concise, though it could include a bit more detail without becoming verbose.

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 is a simple list operation with three optional parameters and no output schema, the description provides the essential purpose. However, it lacks details such as what the response contains, how filtering by reportTaskStatuses works, or any differences from similar tools like ebay_get_report_task. It is adequate but not comprehensive.

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 documents all three parameters (limit, offset, reportTaskStatuses) with 100% coverage. The description adds no parameter-specific information, so it does not compensate for anything the schema already provides. Baseline 3 is appropriate since schema carries the semantic weight.

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 clearly states the action (Get) and resource (report tasks), and mentions the eBay Marketing API. It distinguishes from the singular ebay_get_report_task by being plural, so an agent can tell it fetches a list. However, it is brief and doesn't elaborate on what a report task is, but the purpose is 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?

No guidance is provided on when to use this tool versus alternatives like ebay_get_report_task, ebay_create_report_task, or ebay_get_report. The description does not mention exclusions or prerequisites, leaving the agent to infer usage from the name alone.

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