Create Transformation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose one key behavior (failure on web containers), but it does not mention other aspects such as required permissions, side effects, or what happens on success. This is a minimal but non-trivial disclosure, so a 3 is appropriate.

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 exceptionally concise: two sentences with no filler. The primary purpose is front-loaded, and the critical constraint follows immediately. Every word 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 nested transformation object and the presence of an output schema, the description covers the most critical contextual factor (container type). However, it does not mention any prerequisites, permissions, or side effects of creation, and since there are no annotations to fill these gaps, the description is only partially complete.

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 100% description coverage, so the parameters are fully documented there. The description adds no additional meaning or examples beyond what the schema already provides, meeting the baseline of 3.

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 action ('Create a transformation') and the resource ('in a workspace'), with a specific verb and object. It also includes a critical constraint (server containers only) that distinguishes this from generic create operations and adds meaningful context beyond the name.

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 provides a clear condition for use ('Only server containers accept transformations') and warns that web containers fail, which implicitly tells the agent when not to use it. However, it does not explicitly name alternatives or state when to prefer this over other create_* tools, so the guidance is incomplete.

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