Api user groups object retrieve

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

The description says the endpoint allows user groups to be 'viewed or edited', which directly conflicts with the readOnlyHint=true annotation. Beyond this contradiction, it adds no behavioral context such as return format, permissions, or lookup semantics.

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 a single short sentence with no wasted words, but it is generic boilerplate and not front-loaded with useful operational detail. Its brevity reflects under-specification more than strong conciseness.

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 retrieval tool with one required parameter and no output schema, the description should at least clarify that it returns a single user group by id. Instead it gives a vague 'viewed or edited' statement that omits return behavior and contradicts the read-only annotation.

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?

The tool has one required parameter, 'id', but schema description coverage is 0% and the description does not explain that the id identifies a specific user group. The parameter name and type provide minimal intrinsic meaning, but the description adds no semantic value.

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 restates the resource generically as an 'API endpoint' for user groups but gives only 'viewed or edited' as the operation, which does not precisely describe an object retrieval tool. It also fails to distinguish this tool from sibling user_groups_retrieve, user_groups_list, or user_groups_object_retrieve.

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?

The description provides no guidance about when to use this tool instead of the many sibling user group tools. It does not mention required identifiers, lookup behavior, or any alternative tools for listing or editing user groups.

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