ebay_download_post_order_document

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

Despite the readOnlyHint annotation already signaling this is a safe read operation, the description adds meaningful behavioral context: the output is an embedded PDF, document-state restrictions determine availability, and a specific scope (commerce.post_order.document) is required. No contradiction with the readOnlyHint.

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?

Three sentences with no filler. The core action is front-loaded, followed by the most decision-relevant constraints (document states, permission), so every sentence earns its place.

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?

For a single-parameter read-only download tool, the description covers the output format, access conditions, and required permission. The main gap is that no output schema exists and the description does not describe the response structure or error cases in more detail, but the essential calling context is present.

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 0%, and the description does not explain documentId beyond implying it identifies the post-order document. The parameter's name and constraints (non-empty string) are visible in the schema, but the agent gets no guidance on where to obtain a valid documentId or how it relates to the download states.

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 opens with a specific verb and resource: 'Download a post-order document as an embedded PDF resource.' This is distinct from generic document tools like ebay_get_document and the upload/remove post-order siblings, and the PDF-output detail further narrows the tool's role.

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 about when the tool works: SUBMITTED documents are owner-only, PUBLISHED documents need post-order flow authorization, and expired documents are unavailable. It gives conditional usage guidance but does not explicitly name sibling alternatives or state when not to use this tool in favor of another, 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.