ebay_get_store_tasks

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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds meaningful context beyond that: terminal states, the 24-hour completion horizon, and an active eBay Store subscription requirement with the sell.stores scope.

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?

Three compact sentences, front-loaded with the core action and API name before the usage hint and prerequisite. Every sentence carries information, though the parenthetical API reference is slightly redundant with the tool name.

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 zero-parameter read tool with no output schema, the description covers what the agent needs: what it returns in aggregate, the possible terminal states, and the subscription/scope prerequisite. Only the shape of individual task fields is left unspecified, which is a minor gap.

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 tool takes zero parameters, so the schema has nothing to document and the description has nothing to compensate for. Baseline 4 is appropriate; nothing about parameter meaning is missing or misleading.

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 (List) and resource (asynchronous eBay Store tasks), names the backing API (getStoreTasks), and is clearly distinguishable from the singular sibling ebay_get_store_task. An agent can tell immediately this returns the full task collection rather than one 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?

Gives an explicit use case ("check whether a store category change is still in flight") and a lifecycle constraint (COMPLETED/FAILED within 24 hours), which frames when it is worth calling. It does not explicitly contrast with the singular ebay_get_store_task sibling, so it stops short of full alternative routing.

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