ebay_create_shipping_quote

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

With only readOnlyHint=false from annotations, the description carries real behavioral weight: it discloses the return shape (shippingQuoteId, rates[] fields, expirationDate), the quote's transient expiration, the limited-release restriction (approved developers, USPS only), and a concrete OAuth scope requirement that is not enabled by default plus how to add it. This is well beyond what annotations provide.

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?

Purpose is front-loaded and each sentence is information-dense. The OAuth-scope clause is long and slightly costly to read, but it is genuinely necessary context for a limited-release API rather than padding.

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 explains the return values (shippingQuoteId, rates[], expirationDate), the auth/setup prerequisites, the platform restrictions, and the next step. An agent has everything needed to invoke and act on the result.

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 schema already documents both parameters in detail. The description restates the request structure (orders 1-10, packageSpecification weight/optional dimensions, shipFrom/shipTo) but adds little syntax or format meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Get live shipping rates for one package') and ties itself to the underlying API operation (Logistics API createShippingQuote). An agent can distinguish it from ebay_get_shipping_quote and ebay_create_shipment_from_shipping_quote without opening a schema.

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?

Routes the agent to the follow-up tool explicitly ('buy one with ebay_create_shipment_from_shipping_quote before it expires') and states the prerequisite context (limited release, approved developers). It does not explicitly contrast against the sibling ebay_get_shipping_quote, so it falls just short of the top tier.

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