ebay_get_shipping_fulfillments

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

No annotations exist, so the description must bear the burden. It states the tool gets data (implied read-only via OAuth scope) but does not explicitly confirm no side effects, no pagination behavior, or return format. Adequate but could be more explicit.

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?

Two concise sentences plus OAuth scope lines. Front-loaded with main purpose. No wasted words. 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?

No output schema, so description should explain what is returned. 'Get all shipping fulfillments' is vague; it doesn't describe fulfillment fields (tracking, status). OAuth scope info is good. Adequate for a simple tool but not complete.

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% (one parameter orderId with description). The description's 'for an order' adds no additional meaning beyond the schema's 'The order ID to get fulfillments for'. Baseline 3 applies as schema does the heavy lifting.

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 shipping fulfillments for an order' uses a specific verb ('Get') and resource ('shipping fulfillments'), clearly differentiating from siblings like ebay_get_shipping_fulfillment (singular) and ebay_create_shipping_fulfillment (write).

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 required OAuth scopes, which is helpful for authentication context, but lacks guidance on when to use this tool vs alternatives (e.g., ebay_get_shipping_fulfillment for a single fulfillment). No when-not-to-use or alternative indications.

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