list_layers

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

The description discloses the key behavioral constraint: it operates on the 'active sprite,' not on any other sprite. It also implicitly indicates a read-only operation via 'List.' However, it does not specify the return format or behavior when no active sprite exists.

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 extraneous words. It efficiently conveys the entire purpose.

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?

For a simple no-argument list operation, the description fully captures the tool's functionality. The lack of an output schema is not addressed, but the expected result (a list of layers) is inferable from the name and description.

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 tool takes no parameters, so the schema fully documents the inputs. The description adds no parameter details, but none are needed. Baseline for 0 params is 4.

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 states the tool's function: enumerating all layers within the active sprite. It uses a specific verb ('List') and resource ('layers'), and it is distinct from sibling tools such as get_active_layer, add_layer, or remove_layer.

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 the appropriate context: whenever the user needs a complete inventory of layers in the currently active sprite. It doesn't explicitly contrast with alternatives, but the scope ('active sprite') and the verb 'list' make the usage obvious. No exclusions are mentioned.

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