Api user groups destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description says groups can be 'viewed or edited' — implying a read/update operation and omitting deletion entirely. It adds no context about what gets destroyed or whether deletion cascades, contradicting the destructive annotation.

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?

A single short sentence, but its brevity comes from boilerplate rather than precision — it is under-specified, not concise, and the only content it does convey is wrong for this endpoint.

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 mutation with no output schema, the description should at minimum state that it permanently removes the group and what happens on success or failure. It supplies none of that and instead describes viewing/editing.

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%, and the description says nothing about the single 'id' parameter. The parameter is self-explanatory as an identifier, but the description makes no attempt to compensate for the missing schema documentation.

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 names the resource (user groups) but pairs it with the generic verbs 'viewed or edited', never stating that this endpoint deletes a group. The tool name ends in '_destroy', so the description actively misdirects an agent about the operation.

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 guidance on when to use this tool versus siblings such as user_groups_update, user_groups_partial_update, or user_groups_retrieve. An agent gets no signal that this is the irreversible delete path rather than the edit path the text suggests.

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