Cancel CityJSON upload

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

With no annotations, the description carries the full behavioral burden. "Discard" hints at a destructive operation, but it never states whether the upload and its uploaded chunks are permanently removed, whether the action is reversible or resumable, whether special permissions are needed, or what error occurs for an invalid or already-finished upload.

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?

A single short sentence with zero filler, and the key concept (discard an unfinished upload) is front-loaded. It is efficient but borders on under-specified rather than being tight.

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?

For a destructive, annotation-free cancel operation with an undocumented required parameter and no output schema, the description leaves out essential context: irreversibility, the origin of upload_id, and expected outcomes. An agent could invoke it but cannot predict its 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?

Schema description coverage is 0%, so the only parameter, upload_id, has no documentation anywhere beyond its name and UUID format. The description does not explain where an agent obtains the upload ID (presumably from cityjson_upload_start) or that it must reference a still-open upload.

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 names a specific verb and resource ("Discard an unfinished CityJSON upload"), which cleanly separates it from siblings like cityjson_upload_finish and cityjson_upload_chunk. It stops short of naming those alternatives explicitly, but the intent is unambiguous.

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 only implied: the qualifier "unfinished" signals the tool applies to an in-progress upload, so an agent can infer it is not for completed uploads. There is no explicit statement of when to choose cancel versus finish, or what happens if the upload is already complete.

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