delete_upload_id

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

No annotations provided, so the description bears full burden. It mentions 'closing the connection if needed' but does not disclose side effects, required permissions, or error handling beyond listing error codes. Behavioral traits beyond the action are minimal.

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 short and front-loaded: first sentence gives the action, second lists error codes. While it could be more structured, it is efficient with no extraneous content.

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?

The tool has only one parameter and an output schema, but the description does not mention return values or behavior after deletion. For a simple tool, it is minimally adequate but lacks detail on what the output schema contains or any side effects.

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?

The input schema has one required parameter 'id' with type string, but the description does not explain what 'id' represents (e.g., upload ID). With 0% schema description coverage, the description fails to add meaning to the parameter.

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 the tool deletes a FileUpload and optionally closes a connection. The verb 'delete' and resource 'FileUpload' are specific, though it does not distinguish from siblings like delete_upload_id_cancel or delete_upload_clean.

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?

No guidance on when to use this tool versus alternatives such as delete_upload_id_cancel or delete_upload_clean. It lacks context on prerequisites or appropriate scenarios.

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