DELETE /groups/{id}

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered structurally. The description adds nothing beyond that — it does not say what happens to group members, associated assets, or whether the deletion is soft-deletable, which for a destructive operation on a group is the key missing context.

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?

Very short and front-loaded with the HTTP path and verb, so nothing is buried. But the second sentence is pure generator boilerplate ("Generated from Snipe-IT OpenAPI operation groupsid-3") that consumes space without informing the agent.

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 delete with no output schema and no annotations about side effects, the definition should explain consequences (member removal, cascade effects) and the SNIPEIT_CONFIRM_WRITES condition. Neither appears, leaving the agent under-informed before an irreversible action.

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 100%, and the schema already documents id ("Group ID") and the conditional confirm constant. The description adds no parameter meaning, so baseline 3 applies.

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 and resource ("Delete a group"), which is understandable on its own. However, there are at least four other siblings named snipeit_gen_groupsid_1/_2/_4 sharing the same /groups/{id} path, and the description gives no basis for distinguishing this one from them.

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?

No guidance on when to use this vs. the other groups/{id} operations, no prerequisites, and no mention of the confirmation requirement or how to recover if the wrong group is deleted. The agent must infer everything from the name and schema.

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