ebay_get_shipping_fulfillments

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

With no annotations provided, the description carries full burden. It discloses the required OAuth scope, which is behavioral, but does not mention idempotency, rate limits, return format, or potential data limits. A read operation is implied, but not explicitly stated.

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 two sentences: the first clearly states the purpose, the second provides necessary OAuth scope information. No unnecessary words or repetition.

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 simplicity (one required parameter, no output schema), the description covers the essential purpose and authorization needed. It could be improved by noting the return type or any pagination, but it is generally complete for its complexity.

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 covers 100% of parameters with descriptions. The description adds no additional meaning beyond stating the scope. According to guidelines, high schema coverage warrants baseline 3, so no extra credit.

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'), the resource ('all shipping fulfillments'), and the context ('for an order'). It distinguishes from the singular sibling 'ebay_get_shipping_fulfillment' by specifying 'all' and from 'ebay_create_shipping_fulfillment' by indicating retrieval.

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 provides clear context for when to use the tool (to retrieve all shipping fulfillments for a given order) and includes required OAuth scopes. It does not explicitly exclude alternative tools or provide when-not-to-use guidance, but the purpose is sufficiently clear for selection.

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