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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false. The description adds no behavioral context such as whether renaming overwrites an existing name, what permissions are required, or what side effects occur, so it contributes nothing beyond the 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 single sentence is short but under-specified rather than usefully concise. It fails to front-load any meaningful scoping, effect, or parameter guidance.

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 two-parameter mutation with no output schema and 0% schema description coverage, the description is incomplete. It omits parameter semantics, side effects, and usage guidance; the annotations provide only generic safety hints.

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 0% with two required parameters, and the description does not explain whether "group" is an ID or name or what format or constraints apply to "name". It only weakly implies that "group" is the target and "name" is the new value.

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 "Name a group" essentially restates the title "Name group" and adds no scope, effect, or distinguishing detail. It does not help an agent tell this apart from related sibling tools such as group or ungroup.

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?

There is no when-to-use guidance, prerequisite information, or comparison to alternatives. Given the large set of sibling tools, the definition gives no basis for choosing name_group over group, ungroup, or other group-related operations.

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