ebay_get_notification_destinations

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

The description mentions pagination, which is already implied by the continuationToken parameter. With no annotations provided, the description fails to disclose behavioral traits like rate limits, authentication requirements, or whether the operation is read-only.

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 concise sentence. However, it lacks front-loaded key information that would aid quick comprehension, such as the fact that it returns a list of destinations.

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's complexity (paginated list with no output schema), the description omits important details like the structure of returned destinations (e.g., items array, total count). This forces the agent to rely on implicit knowledge or trial-and-error.

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%, so the baseline is 3. The description adds the word 'paginated' but does not enrich parameter meaning beyond what the schema already provides (e.g., limit range, continuationToken purpose).

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 tool retrieves all notification destinations with pagination. It distinguishes from its singular counterpart (ebay_get_notification_destination) through the plural 'destinations', but does not explicitly differentiate from other sibling tools like ebay_get_notification_subscriptions.

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 such as ebay_get_notification_destination or ebay_get_notification_subscriptions. There is no mention of prerequisites, context, or scenarios.

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