Preview AST transforms

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

With no annotations, the description discloses two behavioral traits: transforms are deterministic and the diff is bounded. It also implies a non-destructive preview operation. However, it does not detail error handling or behavior with invalid transforms, so it earns a 4 rather than a 5.

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?

The description is a single, front-loaded sentence with no wasted words. It states the action, scope, and return type efficiently.

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?

The tool has only two parameters, but the description omits important context such as how the diff is formatted, whether transforms are applied in order, or any prerequisites. It covers the core preview behavior but leaves room for ambiguity.

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 0%, so the description must compensate. It does not explain that 'code' is JavaScript source or what 'transforms' actually does beyond the name. The schema's enum helps, but the description adds no parameter meaning.

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 uses the specific verb 'Preview' and clearly identifies the resource ('supported deterministic JavaScript transforms') and the output ('bounded line diff'). This distinguishes it from sibling tools like ast_transform_apply (which applies) and ast_transform_chain (which chains).

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 implies a pre-application preview use case but provides no explicit guidance on when to use this instead of ast_transform_apply, ast_transform_chain, or transform_workbench. No exclusions or alternatives are mentioned.

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