ebay_upload_payment_dispute_evidence_file

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

No annotations provided, so description carries full burden. It discloses the return value and required scope, but lacks details on file limits, accepted formats, or error conditions. Adequate but minimal beyond basic purpose.

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?

Extremely concise—two sentences plus scope info. No filler, every sentence adds value (purpose, return value, scope). Well front-loaded.

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 simple upload tool, description covers purpose, return value, and scope. Lacks output schema details but return type is implied. Slightly incomplete regarding file constraints but overall adequate.

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 descriptions. The description adds examples (shipping receipt, photos) and clarifies that data is Base64-encoded, enhancing understanding beyond the schema.

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 states 'Upload a file as evidence' with specific examples (shipping receipt, photos) and clarifies the return value (file ID for add_evidence), clearly distinguishing it from sibling tools like add_payment_dispute_evidence.

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?

Provides required OAuth scope and states the file ID is for use with add_evidence, indicating this is a preparatory step. However, it does not explicitly mention when not to use the tool or list alternatives.

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