POST /groups

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds no behavioral context beyond repeating the endpoint. It doesn't mention the confirm='YES' write gate, permission requirements, or what happens on duplicate group names.

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 short and front-loaded, but the second sentence ('Generated from Snipe-IT OpenAPI operation groupsid-1') is pure filler that adds no actionable information.

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 write operation with no output schema and only 50% parameter coverage, the description should explain the confirm gate and the created-group response or failure modes. It omits all of this, leaving real gaps for an agent invoking a mutating endpoint.

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 only 50%, and the description adds nothing about the body fields (name required, permissions) or the confirm parameter. It leaves the agent to infer parameter meaning entirely from the nested schema.

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 ('Create a group') and restates the HTTP endpoint, so the core action is unambiguous. However, it does nothing to distinguish this from the many sibling group tools (snipeit_gen_groupsid, _2, _3, _4), and the tool name's '_1' suffix actually suggests an ID-based operation rather than creation, which creates ambiguity.

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 versus sibling group tools or the generic snipeit_raw_request. The 'POST /groups' prefix implies creation but gives no prerequisites, permissions, or conditions for selecting it over alternatives.

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