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

The description explicitly says the tool can delete layer groups, but the annotations declare destructiveHint=false. That is a direct contradiction for a tool whose stated scope includes deletion. The expectedSpecVersion note adds useful stale-write context, but the annotation conflict is a serious transparency problem.

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?

Two sentences, both front-loaded and free of filler. The action scope comes first, followed by the only non-obvious constraint.

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?

The description covers the tool's multi-action purpose and the versioning guard, but a mutation tool with a delete action and no output schema would benefit from clearer action-specific consequences. It is minimally adequate given the rich nested schema.

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 reported as 0%, but the nested schema properties do document action, group fields, title, and layerIds. The description adds meaningful semantics only for expectedSpecVersion (stale-write prevention), while projectId and action-specific requirements remain largely schema-defined.

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 specific verbs and a clear resource: "Create, update, delete, or assign layer groups in a project map." That distinguishes it from sibling tools like project_add_layer or project_reorder_layers, though it does not explicitly name an alternative.

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 usage through the action list and explains that expectedSpecVersion prevents stale writes, but it does not say when to choose this tool over related siblings such as project_add_layer or project_remove_layers, nor does it state exclusions or preconditions.

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