Api user groups create

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the write shape is known from structured data. The description adds nothing — no mention of required permissions, what happens on duplicate group names, or what the response contains — and its 'viewed' wording sits awkwardly against a non-read-only create endpoint.

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, but brevity here comes from under-specification, not efficiency: a single boilerplate sentence that communicates no operation-specific 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?

A create endpoint taking an untyped body object, with no output schema and no annotations covering payload shape, needs the description to explain the request body and the create semantics. Neither is present, so an agent cannot call this correctly without guessing.

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 one free-form 'body' parameter with 0% schema description coverage and no required fields, and the description says nothing about what the body should contain (group name, permissions, users). With a completely opaque anyOf object, the description carries the full burden and fails to.

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 generic Django-REST boilerplate ('API endpoint that allows user groups to be viewed or edited') and never states that this tool creates a user group, so the specific verb in the tool name is not reflected. It also blurs scope by implying view/edit operations, making it hard to distinguish from the sibling _list, _retrieve, and _update tools.

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 statement of when to use this tool versus the many sibling user-group endpoints (_list, _retrieve, _update, _partial_update). The phrase 'viewed or edited' actively muddies the selection decision rather than resolving it.

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