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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered. The description adds a delete-intent guard ('Delete only when the user asked'), which is useful, but says nothing about irreversibility or what happens to member components when a group is deleted.

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?

Four short sentences, front-loaded with the operation and then conditional rules. The action enumeration is necessary because the schema has no enum, so nothing is wasted.

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 destructive, multi-mode tool with no output schema, the description omits the meaning of 'slug' and the side effects of delete on grouped components. Adequate to invoke correctly in the common case, but not fully 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?

With 0% schema coverage, the description carries the burden and mostly delivers: it supplies the action value set and which params each action requires. 'slug' is required but never explained, which is the one real 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?

States a specific verb set (create/update/delete) and resource (component group), which is clearly distinct from the sibling create_component/update_component tools. It doesn't explicitly say 'for groups, not individual components', but the resource naming does the differentiation work.

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?

Gives a real exclusion rule ('Delete only when the user asked') and conditional requirements per action, which is unusually actionable. It stops short of naming alternatives for component-level operations, so it's clear context without a full when/when-not map.

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