flatten_sprite

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

The description includes the phrase 'in place', signaling that the tool mutates the sprite. However, without annotations, it lacks details on permanence, side effects (e.g., lost layer properties), or undo capability. This is adequate but not comprehensive.

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 extremely concise, using a single phrase and parenthetical. It front-loads the action and scope, with no wasted words. However, the brevity sacrifices some completeness for the parameter.

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?

Given the lack of output schema and no parameter description, the description is incomplete. It does not explain the role of 'filename', expected behavior on failure, or any contextual prerequisites like an open sprite. The tool is simple, but more context is needed.

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 sole parameter 'filename' has 0% schema description coverage, and the tool description provides no additional meaning about what 'filename' refers to (e.g., the sprite to flatten). The agent is left to infer the syntax and semantics.

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 states the action 'flatten' and the resource 'all layers into a single layer', making the core purpose clear. However, it does not explicitly differentiate from similar sibling tools like 'merge_layer_down', though the phrase 'all layers' implies a broader scope.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or explicit exclusions. The description only states what it does, not when or why to use it.

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