Upload progress

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

The description adds meaningful behavioral context beyond the annotations: it explains what each listing entry contains (status, share link when done, reason if not run) and defines when status is 'done'. However, it does not cover pagination, error behavior, or authentication, so it is not fully comprehensive.

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?

The description is two compact sentences, front-loaded with the tool's purpose and immediately followed by useful return-value detail. Every sentence contributes directly to understanding what the tool reports.

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 must explain return values, and it does so by listing per-listing status, share link, and reason, plus the meaning of 'done'. It leaves out edge cases such as invalid upload IDs or pagination, but is otherwise sufficient for a simple read-only progress tool.

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 100% and the sole parameter is already documented as 'The id upload_listings returned.' The description adds no additional meaning about the upload_id parameter, so it meets the baseline for high schema coverage.

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 that this tool reports an upload's progress, including per-listing status, share link once a report is done, and reason for not running. It does not explicitly differentiate itself from siblings such as list_listing_uploads or upload_listings, so it falls short of a 5.

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?

Usage is implied through the description ('An upload's progress') and the schema note that upload_id comes from upload_listings, but there is no explicit guidance on when to use this versus list_listing_uploads or upload_listings. The reader can infer the context but must do some work.

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