bw_adso_transformations

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

With no annotations, the description carries the behavioral burden. It usefully discloses that lookup is by name search and that TRFN titles encode SOURCE -> TARGET, but it does not describe pagination, return shape, error behavior, or whether the ADSO can appear on either side of the relation.

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?

Two sentences, front-loaded with the action and resource, and the second sentence adds a genuinely useful output-semantic detail. No filler or schema repetition.

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 simple two-parameter get tool the description covers the core entity and a key semantic, and outputPath is fully described in the schema. Still, with no output schema it leaves return structure and matching behavior somewhat underspecified, making it minimally viable rather than 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?

Schema coverage is 100%, and outputPath is already documented in detail inside the schema. The description adds only the 'name search' nuance for adsoName, which is helpful but not required; baseline 3 is appropriate.

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 names a specific verb and resource ('Get Transformations related to an ADSO') and adds the search mechanism ('via name search'). It does not explicitly name a sibling to contrast with, so it stops short of full differentiation, but an agent can tell this from DTP/dataflow tools.

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 intended context is implied: use this when you need transformations associated with an ADSO, especially since each TRFN title exposes a SOURCE -> TARGET relation. However, it gives no explicit when-not-to-use guidance or alternatives such as bw_adso_dtps, bw_trfn_details, or bw_dataflow_get.

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