Delete temporary upscaled image files from Google Cloud Storage after download to free storage and avoid clutter. Use this cleanup step once the upscaled file is no longer needed.
Delete temporary upscaled file from GCS after downloading. DELETE /api/v1/generate/image/upscale?url=...
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Signed GCS URL from upscale_image response |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It clearly signals a destructive action and identifies the exact object being removed ('temporary upscaled file from GCS'), which helps prevent misuse. It does not disclose idempotency, auth requirements, or behavior on invalid/missing URLs, but the simple cleanup context softens that gap.
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?
One tightly written sentence carrying action, object, timing, and endpoint with zero filler. The most important information is front-loaded.
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 one-parameter cleanup operation, the description provides the essential workflow context: delete the temporary GCS file after downloading it. It leaves error behavior and idempotency unspecified, but an agent has enough to invoke it correctly in the intended pipeline.
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 already provides strong meaning: the single parameter is a signed GCS URL from upscale_image response. The description adds only the endpoint query-string form, so it does not need to compensate further.
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?
States a specific action (delete) and resource (temporary upscaled file in GCS), reinforced by the HTTP DELETE method and path. It clearly distinguishes itself from sibling generation/upscale tools as the cleanup counterpart.
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?
Explicitly conditions use on 'after downloading', giving clear timing context. It does not name alternatives or exclusions, but no competing delete tool exists among siblingsebb, and the reference to upscale_image makes the workflow relationship implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.