delete_upload_id_cancel

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

No annotations, so description carries full burden. It discloses the cancel action closes connection, precondition on status, and error codes. Lacks side-effect details but sufficient for a destructive cancel operation.

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?

Short and to the point, includes precondition and error codes in two sentences. Could be slightly more structured, but 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 essential: action, precondition, error codes. Missing return value context (though output schema exists). Does not mention idempotency or success indicator. Adequate for a simple one-param delete, but could be improved.

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?

Single required parameter 'id' with 0% schema description coverage. Description does not explain what the 'id' represents beyond 'the given FileUpload', adding minimal value. Agent must infer that id refers to a FileUpload identifier.

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?

Clearly states it cancels a FileUpload by closing the connection, with precondition on upload status. Distinct from sibling delete upload tools by specifying 'cancel' and closing connection.

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 precondition (upload must be in_progress) and lists error codes. However, no explicit guidance on when not to use or alternatives among sibling delete upload tools like delete_upload_id or delete_upload_clean.

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