ebay_get_notification_subscriptions

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

No annotations are provided, so the description carries the full burden. It only mentions pagination, but fails to disclose authentication requirements, rate limits, or any side effects. Minimal behavioral context.

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 very concise with one short phrase. It is efficient but could benefit from a slightly more structured format (e.g., stating what it returns). No wasted words.

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 does not explain the return format (e.g., list of subscription objects). While parameters are fully documented, the lack of output description leaves agents uncertain about the response structure.

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 coverage is 100% with both parameters fully described (limit with range, continuationToken as pagination token). The description adds '(paginated)' which reinforces pagination but does not add semantic value beyond the 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 'Get all notification subscriptions (paginated)' clearly specifies the verb (Get), resource (notification subscriptions), and scope (all, with pagination). This distinguishes it from sibling tools like ebay_get_notification_subscription (singular) and CRUD operations.

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?

The description implies usage for listing all subscriptions with pagination, and the name contrasts with ebay_get_notification_subscription (singular). However, no explicit when-to-use or when-not-to-use guidance is provided, and alternatives are not mentioned.

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