trigger_upload

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

No annotations are provided, so the description partially compensates by noting the 'wait' parameter can block for up to 120s and that --allow-write is needed. However, it fails to disclose timeout behavior, idempotency, or side effects, leaving gaps.

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 extremely concise, with two clear sentences plus parameter definitions. Every sentence adds value, and the structure is front-loaded with the core purpose.

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?

Given no annotations, the description is adequate but incomplete. It does not explain return values (though output schema exists), error scenarios, or what constitutes an 'upload run'. More detail on expected behavior would improve completeness.

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?

With 0% schema description coverage, the description successfully adds meaning: 'upload_id' is identified as the upload to run, and 'wait' is explained as blocking up to 120s. This goes beyond the schema's basic type and default information.

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 'Trigger an upload run,' using a specific verb and resource. It distinguishes from sibling tools like 'trigger_pipeline' and 'list_uploads' by focusing on upload runs.

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 mentions 'Requires --allow-write,' implying a permission requirement, but lacks explicit guidance on when to use this tool vs alternatives like 'bulk_import' or 'trigger_pipeline'. Usage context is implied but not clearly stated.

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