delete_text_to_image_task

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

No annotations are provided, so the description carries the full burden, yet it omits critical traits for a destructive operation: whether deletion is permanent or reversible, whether it requires ownership or auth, what happens to an in-progress or completed task, and the response on success or failure.

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 single sentence is front-loaded and contains no waste, but its brevity reflects under-specification rather than efficient information density; it fails to earn its place as sufficient documentation.

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 mutation tool with no output schema and an undocumented parameter, the description leaves out irreversibility, error behavior, and parameter meaning, making it inadequate for confident invocation.

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 coverage is 0% and the sole parameter task_id has no description in either schema or description, so the tool does not clarify whether it refers to a task ID from a create_* response or a list_* entry. With one required parameter undocumented anywhere, the description does not compensate for the coverage gap.

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 states a specific verb and resource ('Delete a text-to-image task'), which is marginally more than the tool name alone, but it adds no distinguishing detail about what deleting entails or how it differs from sibling delete tools beyond the resource name already in the tool identifier.

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?

There is no guidance on when to use this tool versus the many sibling delete_* tools, no prerequisites, and no mention of when deletion is appropriate or when a retrieve_* call should precede it. Usage is only implied by the verb.

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