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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the response includes source code, which signals potentially large or sensitive payloads. It does not say what happens when the library has no source, nor whether the call is expensive.

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?

A single short sentence with no wasted words, and the most useful detail (source code included) is placed where it is read first. It is arguably too terse for the gaps it leaves, but there is no filler to cut.

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 two-parameter read-only fetch with no output schema, the definition covers the basic contract and notes the source-code payload. It leaves out the shape and size of the return, the meaning of workspace_id, and any relationship to get_transformation, which is a moderate but not severe gap given the annotations.

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 50%: library_id is documented as coming from list_transformation_libraries, but workspace_id has no description anywhere. The tool description contributes nothing about either parameter, so the undocumented half remains unexplained.

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?

States a specific verb (Get) and resource (transformation library) and adds that source code is included. It is distinguishable from the sibling list_transformation_libraries, though it does not explicitly differentiate itself from get_transformation, which sits adjacent in the tool set.

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 no guidance on when to use this tool versus list_transformation_libraries, get_transformation, or sample_transformations. The only indirect hint is the schema note that library_id comes from list_transformation_libraries, which implies a list-then-get flow but is never stated as usage guidance.

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