bw_trfn_create

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

With no annotations provided, the description carries the full behavioral burden. It discloses server-side id generation, hydration of source/target elements and default rules, the trfnId + hydrated XML return, the $TMP package default, and the transport requirement for real packages. It stops short of explicitly stating whether the transient artifact persists without the follow-up save, though 'then use ... to finish' implies it does not.

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 compact and front-loaded, with the purpose in the first sentence. It packs the key behavioral facts, default behavior, return value, and next-step tools into four sentences without repeating parameter-level detail already present in the schema.

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 10-parameter tool with no annotations and no output schema, the description covers the important workflow context: creation, return shape, package/transport coupling, and follow-up tools. It relies on the schema for parameter detail and could add an explicit 'does not persist until a save call' warning, but overall an agent has enough to select and invoke it 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%, so the schema already documents all 10 parameters. The description adds valuable semantic context beyond the schema by explaining that packageName defaults to $TMP)Skip, that a real package requires transport, and that this is a create-only step with follow-up tools for rules and saving.

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 opens with a specific verb and resource: 'Create a transformation via the 8TRANSIENT transient flow.' It clarifies this is the Eclipse-wizard-equivalent creation step/allocation, and it distinguishes itself from save/activate siblings by explicitly naming follow-up tools needed to finish. The server-minted id and hydrated-XML return further define the tool's specific scope.

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 gives a clear progression: create, then use bw_trfn_auto_map_and_save / bw_trfn_add_rules_and_save / bw_trfn_check to finish. It also explains the packageName/transport condition for registering in a workbench request. It does not explicitly say 'do not use this to save/activate,' but the transient-flow framing and 'to finish' provide strong contextual guidance.

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