Create Layer Group

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

Without annotations, the description only indicates the creation action. It omits details on error handling (e.g., duplicate group name, missing parent), side effects, or success feedback, which is minimal for a mutation tool.

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 one sentence with two clauses, front-loading the primary action and appending the optional parameter. Every word is necessary, 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 creation tool with two parameters and no output schema, the description adequately explains the core functionality. However, it could be more complete by noting interaction with existing groups, error states, or confirmation of success.

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 adds basic meaning to the two parameters: 'name' is the group name, 'parent' is optional and specifies the parent group. However, it does not clarify expected formats (e.g., full path) or constraints, adding only marginal value over the schema.

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 creates a new layer group in the layer tree, using a specific verb and resource. It distinguishes from sibling tools like move_layer_to_group and remove_layer, but does not mention uniqueness constraints or layering order.

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 explicit guidance on when to use this tool versus alternatives. The mention of optional parent group implies hierarchical use, but no prerequisites or when-not-to-use conditions are stated.

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