bw_dtp_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 burden and does well: it reveals the lock/PUT/activate/unlock sequence, marks activation as optional, and states that a compact projection is returned unless outputPath is set. It does not explain failure behavior or whether unlock still happens after an error, but this is still substantive disclosure.

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 core pipeline, followed by parameter preferences and return behavior. Every sentence earns its place, though terms like 'PUT' and 'TRKORR' assume domain familiarity.

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?

The main call path, parameter preferences, transport handling, and return behavior are covered, which is good for a tool with 8 parameters and no output schema. Still, it omits how autoActivate relates to the optional activation, what happens on failure, and when to prefer bw_dtp_activate instead.

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 description coverage is only 38%, so the description partly compensates by explaining the relationship between xmlPath/xmlContent, transport/createTransport, and outputPath. However, it leaves autoActivate, transportDescription, and id semantics mostly to inference, and it does not explicitly map 'optional activate' to autoActivate.

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 identifies a combined pipeline for saving and activating a DTP object ('lock → PUT → (optional) activate → unlock') and names the preferred input path. It is specific about the resource type via the tool name and sibling context, but it does not explicitly differentiate this tool from bw_dtp_activate or bw_dtp_create.

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 concrete conditional guidance: prefer xmlPath over xmlContent, use transport=<TRKORR> or createTransport=true when a transport is required, and set outputPath for full detail. It lacks an explicit 'when not to use this tool' or a comparison with sibling save/activate tools, but the context is clear enough for most selections.

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