ebay_download_shipping_label_file

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

Goes well beyond the readOnlyHint annotation by disclosing that the Logistics API is limited release, USPS-only, and requires the sell.logistics scope which is not requested by default, including the remediation (add to EBAY_OAUTH_SCOPES and re-consent). This is exactly the kind of auth and access context that prevents failed calls.

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-loads the action and resource, then packs prerequisites and auth constraints into a compact follow-up. The second sentence is dense and runs long, but nearly every clause carries operational value.

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 supplies the return form (embedded PDF resource), the required prerequisite call, and the full auth/eligibility conditions. An agent has everything needed to invoke this correctly or determine it cannot.

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% and the schema already documents shipmentId as the ID returned by ebay_create_shipment_from_shipping_quote. The description repeats that provenance with no additional syntax or format detail, 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 ('Download the shipping label of a shipment as an embedded PDF resource') and names the underlying API operation (downloadLabelFile). This clearly distinguishes it from adjacent siblings like ebay_get_labels, ebay_get_handover_sheet, and ebay_get_tracking.

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?

Gives a concrete precondition: the shipmentId comes from ebay_create_shipment_from_shipping_quote, which routes the agent to the correct upstream call. It also states eligibility gating (approved developers, USPS only), though it does not explicitly contrast against alternatives like ebay_get_labels.

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