ebay_fetch_payment_dispute_evidence_content

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

No annotations are provided, so the description carries full burden. It states 'Download evidence file content', implying a read operation, but does not disclose side effects (none expected), file size limits, binary vs text content, or error behavior. The OAuth scope is helpful but insufficient.

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 short sentences with no wasted words. The required scope is clearly listed. Efficient and easy to parse.

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 exists, and the description does not explain the return format (e.g., binary file, base64, JSON). For a download tool, this is a critical gap. Also missing details about prerequisites (e.g., dispute must exist, evidence must be uploaded). Incomplete given the tool's complexity.

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% with clear parameter descriptions for paymentDisputeId, evidenceId, and fileId. The description adds no additional parameter-level meaning beyond summarizing the action. Baseline 3 is appropriate.

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 clearly states the verb 'Download' and the resource 'evidence file content from a payment dispute', which distinguishes it from sibling tools like 'ebay_upload_payment_dispute_evidence_file' (upload) and 'ebay_add_payment_dispute_evidence' (add evidence). No ambiguity.

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 includes OAuth scope information but provides no guidance on when to use this tool versus alternatives such as ebay_get_payment_dispute or ebay_add_payment_dispute_evidence. No exclusions or context for decision-making.

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