motion_list_layers

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

With no annotations, the description carries the burden of behavioral disclosure. It details the output contents, which is useful, but does not explicitly state that the operation is read-only, has no side effects, or requires an open template. The verb 'List' suggests safety but is not explicit.

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, well-structured sentence that front-loads the action and resource, then lists the output fields. Every word contributes information with no redundancy or filler.

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?

While the output schema likely covers return values, the description omits any explanation of the input parameter 'path' and lacks usage guidance. For a tool with a single undocumented parameter, the description should at least hint at what the path refers to, which it does not.

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 has a single 'path' parameter with no description, and the tool description does not explain what 'path' refers to (template file path, layer path, etc.). This is a critical gap especially since schema description coverage is 0%, leaving the user to guess.

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 action (List), the resource (every layer in the template's layer tree), and the specific fields returned (id, name, factory kind, nesting depth, locked). It distinguishes itself from the sibling motion_list_text_layers by specifying 'every layer' rather than only text layers.

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 tool is for obtaining a complete layer list, but it does not explicitly mention when to use it versus alternatives like motion_list_text_layers. No exclusion or conditional guidance is provided, though the sibling name provides a subtle hint.

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