list_layers

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

With no annotations, the description carries the burden. It discloses the read-only nature via 'List' and notes the order, but it doesn't clarify what 'root layers' means (e.g., whether nested/layer groups are excluded) or any other behavioral details. It's adequate but minimal.

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 with no filler. Every word is meaningful and the structure is clear, making it highly concise.

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 list operation with an output schema, the description is nearly sufficient, but it omits any connection between the action and the required 'image_id' parameter. Also, 'root layers' could benefit from a brief clarification. Overall, it's adequate but not complete.

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 description makes no mention of the 'image_id' parameter. Schema coverage is 0%, so the description fails to clarify what the parameter refers to. The agent must rely on the parameter name alone, which is a significant gap.

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 uses the specific verb 'List' with the resource 'root layers' and specifies 'top-to-bottom order', clearly differentiating this from other layer operations like get_layer_info or create_layer. It's unambiguous about what it returns.

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 tells you what it does but doesn't explicitly say when to use it over alternatives, nor does it state any exclusions. The usage is implied but not directly guided, which is a minor gap given sibling tools like get_layer_info.

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