GET /groups/{id}

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that—no note on permissions required, response shape, or 404 behavior for a missing group.

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?

It is short and front-loaded, which is good, but the second sentence ("Generated from Snipe-IT OpenAPI operation groupsid") is generator boilerplate that gives the agent no usable 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 simple, fully-annotated single-param read, brevity would be acceptable—except that the sibling list contains five ambiguous groupsid lookups and the description offers no disambiguation. An agent has no basis to choose this one over gen_groupsid_1 through _4.

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?

There is a single parameter with 100% schema description coverage ("Group ID"), so the schema carries the semantics. The description adds nothing further, which is the baseline case for a one-param tool.

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?

"Return a group" names a verb and resource, so the basic purpose is recoverable. But it is essentially a restatement of the HTTP operation and gives no way to tell this apart from the four near-identical siblings (gen_groupsid_1, _2, _3, _4), which all appear to return a group by id.

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 the other groupsid variants or snipeit_raw_request. Usage is only inferable from the HTTP path, and no exclusions or alternatives are named.

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