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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the safety bar is partly met. The description adds a genuinely useful behavioral fact beyond annotations: name uniqueness is enforced within the type, so a duplicate will fail. It does not describe what is returned or whether the call is idempotent on retry.

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?

Two compact sentences, front-loaded with the action and followed by the two constraints that matter (per-type scoping, unique name). The parenthetical type enumeration is the only slightly bulky element, but it usefully illustrates the scoping rule.

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 two-parameter mutation tool with no output schema, the description covers what the tool does and the two constraints on its inputs. It leaves gaps on the return value (created group id/object), error behavior on duplicate names, and whether the type list is exhaustive.

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 0%, so the description must carry parameter meaning, and it does: 'type' is explained as the entity type a group belongs to with concrete examples, and 'name' carries the uniqueness-within-type constraint. The only weakness is that the parenthetical type list is partial ('…') versus the 17-value enum in the schema.

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?

Specific verb + resource ('Create an entity group') with the key qualifier that groups are scoped per entity type. It clearly distinguishes this from sibling create_* tools that create the entities themselves rather than a grouping container, though it never names a sibling explicitly.

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?

Usage is implied by the per-type scoping and the uniqueness rule, which tells the agent a precondition for a successful call. There is no explicit when-to-use vs. update_group, list_groups, or guidance on whether a group must exist before attaching entities.

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