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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses that the operation is irreversible, discards ciphertext, affects composed environments, and returns { ok, group }. This adds meaningful behavioral context about side effects and return shape that annotations alone do not provide, and it does not contradict any annotations.

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 compact and well structured, front-loading the core destructive action, then the irreversibility, then the precautionary guidance, and finally the return value. Every sentence earns its place and there is no filler or redundancy.

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 destructive nature of the tool, the description covers what is deleted, why it is dangerous, how to verify with list_env_groups, an alternative via uncompose_group, and the return shape. With annotations already covering safety hints and schema covering parameters, nothing critical is missing for an agent to decide and invoke the tool correctly.

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 input schema already provides 100% coverage with clear descriptions for both group and org parameters, so the description does not need to add parameter-level semantics. It mentions 'group' in context but adds little beyond the schema; the baseline of 3 is appropriate because the schema already carries the full burden.

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 specific verb 'Delete' and the resource 'a shared group', and goes further to specify that it also removes the group's environments and their secrets. It is well distinguished from sibling tools like delete_app, delete_env, delete_secret, and uncompose_group, so an agent can immediately tell what resource is affected.

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 gives explicit pre-call guidance: check list_env_groups or use uncompose_group before deciding the group is unused. It also instructs the agent to confirm intent before calling, which is essential for a destructive operation. This clearly communicates when to use the tool and what safer alternatives exist.

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