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

Annotations declare destructiveHint=true, idempotentHint=false and openWorldHint=true, which is surprising for something framed as a 'test'. The description does nothing to explain what is destructive, whether the code is sandboxed, whether test runs touch production pipelines, or how errors surface. Since annotations already flag risk, the description should have clarified the side-effect model but instead only restates the name.

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 short sentences, the core action front-loaded and the pointer to sample_transformations second. Nothing is padded or redundant.

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?

With four parameters, no output schema, and a destructive annotation, an agent needs to know what a test run returns (transformed events, errors, logs) and what persists after the call. The description covers neither, so it is adequate but leaves meaningful gaps for a tool flagged as destructive.

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 75% and the schema already documents code format, the input JSON example, and the language enum. The description only alludes to 'sample events' (mapping loosely to input) and adds no syntax or constraint detail for workspace_id, which has no schema description at all. 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 gives a specific verb and resource: testing transformation code against sample events. That distinguishes it in spirit from transformation_test_existing and from get_transformation, though it never explicitly says 'use this for unsaved/new code, not deployed transformations', leaving the distinction to the tool name alone.

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?

It offers one useful routing hint – pull starter templates from sample_transformations – which tells the agent how to bootstrap the code parameter. However, it never states when to prefer transformation_test_existing, nor whether a transformation must already exist in the workspace, so usage is only implied.

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