create_layer

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Create a new layer' without mentioning any side effects, such as whether the layer is automatically made active, what happens to existing layers, or if any permissions are required. The description is entirely insufficient.

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 short (4 words) and front-loaded. However, it is under-specified and sacrifices completeness for brevity. While concise, it fails to provide essential context, making it insufficient for an agent to use correctly.

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 presence of 4 parameters, no output schema, and no annotations, the description should provide more context about the tool's use, such as the return value (e.g., layer ID) or the effect on the document state. The description is completely inadequate for the complexity of the tool.

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 100%, so the schema already documents all four parameters. The description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate as the description does not harm but also does not enhance parameter understanding.

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 'Create a new layer' clearly states the verb (create) and resource (layer). However, it does not distinguish this tool from numerous sibling 'create' tools (e.g., create_document, create_group) or provide context about the layer's context (e.g., in a document). It is minimally adequate but lacks specificity.

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 is given on when to use this tool versus alternatives like organize_document_layers or set_active_layer. The description does not mention prerequisites (e.g., a document must be open) or when not to use the tool. This is a significant gap.

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