bw_set_transformation_runtime

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

With no annotations, the description discloses key behaviors: only changes HANARuntime attribute, idempotent early return, and returns a lock_handle. It lacks details on prerequisites, authorization, or side effects, but is sufficient for a simple mutation.

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?

Three sentences: purpose, constraint, and idempotency/return. No extraneous information. Perfectly front-loaded and concise.

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's simplicity and full schema coverage, the description covers the main functionality. Minor omission: does not explain that bw_activate must be called after using the lock_handle, or require existing object lock.

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?

All 3 parameters have schema descriptions; the tool description adds value by explaining the runtime parameter's effect ('hana sets HANARuntime=true') and the transport parameter's conditional requirement. This enhances understanding beyond the schema.

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?

Clearly states the tool switches Transformation runtime between HANA and ABAP, specifying it only changes the HANARuntime attribute. This differentiates it from siblings like bw_update_transformation or bw_set_transformation_routine.

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?

Explicitly notes that no rule changes are made and that the tool returns early if runtime already matches, providing clear context for when to use. However, it does not explicitly name alternative tools or state when not to use.

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