ebay_get_notification_destination

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

No annotations are provided, and the description states only 'Get', indicating a read operation. However, it does not disclose potential errors, rate limits, or any other behavioral traits. The description partially covers the safety profile but lacks depth.

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 sentence that immediately communicates the action and scope. There is no extraneous information, making it highly concise and well-structured.

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?

The tool has one parameter, no output schema, and no annotations. The description provides a minimal but adequate statement of purpose, but it does not explain what a notification destination is, what the response looks like, or any prerequisites. For a simple get operation, it is slightly lacking in context.

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 has 100% description coverage (the only parameter 'destination_id' is described as 'The unique identifier for the destination'). The tool description adds no further meaning beyond this, so the baseline of 3 is appropriate.

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 a specific notification destination by ID' clearly states the verb (Get), the resource (notification destination), and the scope (by ID). It distinguishes from the sibling 'ebay_get_notification_destinations' which retrieves multiple destinations.

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 does not provide explicit guidance on when to use this tool versus alternatives like ebay_get_notification_destinations or ebay_create_notification_destination. However, the name 'get' for a specific ID implies it is for retrieving a single known destination, which can be inferred from the sibling names.

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