Transform Layer

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

The description states 'Modifies the layer's pixel data destructively,' but annotations set destructiveHint to false. This contradiction undermines transparency, as per the scoring rule for annotation contradictions.

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 concise with two sentences: the first defines the core action, and the second provides usage tips. No redundant information is present.

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 description adequately covers the purpose, destructive nature, pre-use check, and undo capability. However, it lacks details about immediate application and potential effects on layers beyond pixel data.

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?

The input schema covers all 6 parameters with clear descriptions, achieving 100% coverage. The description adds no further parameter details, so a baseline score of 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 clearly specifies the tool's purpose: scaling, rotating, or flipping a layer in-place. It explicitly states the operation is destructive, distinguishing it from other layer manipulation tools like move_layer or set_layer_properties.

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 provides actionable guidance by suggesting using get_layers to check bounds before transforming and using undo to revert. However, it does not explicitly mention when not to use this tool or compare it to alternatives.

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