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

Annotations declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, but the description says only 'test ... against sample events', which reads as harmless. It never explains that the transformation code actually executes, what side effects could occur, or why the operation is flagged destructive — so it adds little beyond the annotation flags and arguably softens them.

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 front-loaded sentence with no filler or repetition. It is efficient, though the terseness leaves no room for structure such as a usage note or return-value hint.

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?

There is no output schema, so the description should explain what a test returns (pass/fail per event, transformed payload, errors) — it does not. Combined with an unexplained destructiveHint and an undocumented workspace_id, an agent cannot predict the outcome or risks of invoking it.

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 67%: 'input' has a detailed JSON example and 'transformation_id' points to list_transformations, while 'workspace_id' is undocumented. The description adds no parameter meaning at all, so the schema does the heavy lifting; baseline 3 is appropriate for this coverage level.

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 ('Test') and resource ('an existing saved transformation') plus the input kind ('sample events'). The word 'existing' implicitly contrasts with the sibling transformation_test_new, so an agent can pick between the two, though the sibling is never named explicitly.

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?

Usage is only implied: 'existing saved transformation' suggests using this for transformations already created, and transformation_test_new for unsaved ones. There is no explicit when-to-use/when-not statement, no prerequisite (e.g., transformation must already exist in the workspace), and no mention of alternatives.

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