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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and idempotency are covered upstream. The description adds no behavioral context of its own: no pagination behavior, no indication of default result volume, no eager/lazy loading traits.

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 extremely short, so there is no wasted wording, but it is a noun fragment rather than a front-loaded action statement. Brevity here comes from under-specification, not disciplined editing.

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?

The tool has four optional parameters, paginated output, and no output schema, so the description must carry the burden of explaining what is returned and how paging behaves. Instead it offers a five-word gloss, leaving the agent to infer result shape and default page size from the schema alone.

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 100%, with page, per_page, type, and search all documented inline, so the baseline is 3. The description's "per entity type" merely echoes the schema's `type` field wording and contributes no additional semantics such as allowed keys or defaulting.

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?

"Entity groups (per entity type)" essentially restates the tool name and title rather than stating what the operation does. The fragment "per entity type" hints at grouping scope but there is no verb or listing action, and nothing distinguishes it from siblings such as create_group or update_group.

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 gives no when-to-use guidance, no alternatives, and no conditions. It never points the agent to create_group/update_group for mutations or to any search tool for text lookup, so selection is left entirely to the tool name.

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