GET /groups

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that – no note on pagination behavior, search semantics, or what a 'group' object contains.

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?

Both sentences are noise: one repeats the title verbatim, the other states OpenAPI codegen provenance that helps no agent. There is no front-loaded explanation of what the endpoint returns or does.

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 six-parameter listing endpoint with no output schema, the description should at minimum describe the returned group records and pagination contract. It leaves the agent to reconstruct behavior entirely from the path and schema, which is inadequate.

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 83%, so the six parameters (name, sort, order, limit, offset, search) are largely documented in the schema itself, giving a baseline of 3. The description contributes no additional parameter meaning at all, so it cannot exceed that baseline.

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 is effectively a restatement of the title 'GET /groups' plus a codegen provenance note. It never says in natural language that this lists user groups, and it does nothing to distinguish it from the many sibling groups endpoints (snipeit_gen_groupsid, _2, _3, _4). An agent must infer resource semantics from the path alone.

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 listing endpoint versus the per-id group endpoints or snipeit_raw_request. No prerequisites, scope, or alternatives are mentioned.

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