bw_trfn_save_and_activate

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

With no annotations provided, the description carries the full disclosure burden and does reveal the mutation sequence (lock/PUT/activate/unlock) and the return behavior (compact projection unless outputPath is set). However, it does not disclose failure semantics — e.g., whether unlock happens if the PUT or activation fails — nor prerequisite/permission requirements, which matters for a write tool with zero annotation coverage.

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?

Four sentences, roughly 60 words, with the core workflow front-loaded before parameter guidance and return behavior. Each sentence earns its place; the only minor blemish is the slightly jargon-dense 'one-stop' opener, but nothing is redundant or bloated.

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 complex 9-parameter mutation tool with no output schema and no annotations, the description covers the essential workflow, the two input modes, transport handling, and output routing. It leaves gaps around the meaning of id (which object is targeted), how autoActivate maps to the '(optional) activate' step, and failure handling — meaningful ambiguities for a write operation of this complexity.

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 only 33%, so the description must compensate; it adds genuine meaning by explaining the xmlPath-over-xmlContent preference and clarifying transport vs. createTransport as alternatives. Yet it does not explain id, timestamp, autoActivate, or transportDescription, leaving most of the undocumented parameter space to inference, so compensation is partial.

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 conveys a specific composite operation ('lock → PUT → (optional) activate → unlock') on a transformation object, which clearly identifies it as a save-and-activate mutation distinct from pure-read siblings like bw_trfn_details and from bw_trfn_create. The 'one-stop' framing plus the resource-specific verb chain is clear, though it never names a sibling explicitly and relies on the tool name to signal the trfn resource type.

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?

Provides concrete conditional guidance: prefer xmlPath produced by bw_trfn_get_xml + outputPath over inline xmlContent, and 'when a transport is required: pass transport=<TRKORR> OR createTransport=true.' This is real context for choosing among parameters, though it does not address when to choose this tool over sibling writers (e.g., bw_trfn_create for new objects, bw_dtp_save_and_activate for DTPs).

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