cancel_transformation

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

No annotations are provided, so the description must fully disclose behavioral traits. It warns of a write operation and requires confirmation, but omits details like irreversibility, permission requirements, side effects on related resources, or what response to expect. The description is insufficient for an agent to understand the full impact of calling this tool.

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 extremely concise: two sentences. The first sentence serves as a critical behavioral warning, and the second clearly states the purpose. No unnecessary words or redundant information. Every part earns its place.

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?

Given the tool has three required parameters, no output schema, and no annotations, the description is too brief. It fails to explain the return format, error handling, idempotency, or post-cancellation state. The agent would need additional documentation to use this tool safely and correctly.

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 100%, providing baseline meaning for all parameters. The description adds value primarily through the schema_file parameter's instruction to read a specific schema file and the general warning. However, the transformation_id parameter lacks additional elaboration beyond its schema description. Overall, the description complements the schema without significantly surpassing it.

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 the action clearly: 'Cancels the execution of the transformation'. It includes a verb ('cancel') and a specific resource ('transformation execution'). However, it does not explicitly differentiate from sibling tools like 'delete_transformation' or 'run_transformation', leaving the agent to infer the distinction. The warning label adds context but not a direct sibling comparison.

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?

The description includes a user confirmation directive ('Confirm with user before calling') but provides no guidance on when to cancel vs. delete or other alternatives. It does not specify prerequisites, conditions for valid cancellation, or scenarios where cancellation is inappropriate. This leaves the agent without enough context to make informed decisions.

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