convert_layer

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered; the description adds nothing further. It never states whether existing pixel data is preserved, whether converting to/from Background flattens anything, or whether the change is undoable, which matters for a layer-type mutation.

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 that packs the three supported conversions without filler. It is efficient, though the colon-list construction is slightly dense and could be split for faster scanning.

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 five parameters (one required), 80% schema coverage, and no output schema, the description need not explain return values, but it should say what happens to the layer's content after conversion. For a mutation tool with no output schema, the absence of any side-effect statement leaves a real gap.

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 80% and the 'save', 'layer', 'sprite', and 'backend' parameters are documented in the schema, so the baseline of 3 applies. The description lists the conversion modes that correspond to the 'to' enum but adds no syntax or defaulting nuance beyond what the schema already provides.

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 names a specific verb (converts) and resource (a layer) and enumerates the three conversion modes, which map cleanly onto the 'to' enum values. It is distinguishable from sibling mutators like update_layer or add_layer, though it never explicitly contrasts itself with them.

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 enumerated conversion directions imply when the tool is appropriate (changing layer type), but there is no explicit guidance on when to prefer it over update_layer or add_layer, and no mention of prerequisites such as needing an open sprite or a tilemap-capable document for the image/tilemap conversions.

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