ebay_get_shipping_quote

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

readOnlyHint=true is already declared, but the description adds genuinely non-obvious context beyond annotations: limited release gating, USPS-only constraint, and the scope that is not requested by default with re-consent requirements. No output schema exists, so the list of returned fields is also useful disclosure.

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?

Front-loaded with the core purpose before the operational caveats. The second sentence is long but every clause (limited release, scope name, key-set remediation) carries actionable information, so it earns its space.

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 compensates by enumerating return contents, and it covers the auth/eligibility prerequisites that would otherwise block a successful call. Nothing essential for correct invocation is missing.

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?

Only one parameter, and schema coverage is 100% — the schema description already explains it is a shipping quote ID returned by ebay_create_shipping_quote. The description restates 'by shippingQuoteId' without adding format, lookup, or error semantics, so the 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 a shipping quote by shippingQuoteId') and enumerates what the response contains (rates, package, addresses, expiry), plus names the underlying API operation. An agent can distinguish this from sibling quote tools such as ebay_create_shipping_quote.

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 gives strong preconditions: limited-release API, eBay-approved developers only, USPS rates/labels only, and the exact OAuth scope required with remediation steps (add to EBAY_OAUTH_SCOPES and re-consent). It does not, however, route the agent to alternatives or state when not to use it, so it stops short of a 5.

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