upload_listing_file

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

No annotations provided, so description must cover behavior. It only describes the basic upload action without disclosing side effects (e.g., overwrite behavior, file size limits, permissions needed). Limited transparency.

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 efficient sentences, front-loaded with action and key constraints. No unnecessary words.

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?

Covers the essential: what, where, and constraint. Lacks details on return values (no output schema) and error conditions, but for a simple upload tool, it's mostly complete.

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?

Adds value beyond schema by specifying file types (PDF, ZIP) and the listing type constraint (must be 'download'). For listing_id, it implies a download listing context. Schema coverage is 67%, so description compensates well.

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?

Description clearly states upload a digital file to a listing, with file type examples and a constraint (listing type must be 'download'). Distinguishes from siblings like upload_listing_image and delete_listing_file.

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?

Implies usage for uploading files to download listings, but no explicit when-not-to-use or alternative tools. The constraint on listing type provides some guidance, but lacks broader context.

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