Create Group

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It openly states the operation is mutating, explains uniqueness constraints, documents that passing model_ids for system groups raises an error, and describes what is returned for each kind.

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 well-structured with a front-loaded summary followed by focused bullet-style explanations. Every sentence adds meaningful context, and the format makes the tag/system distinction easy to parse.

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?

Given the lack of annotations and the tool's branching behavior between tag and system kinds, the description is complete: it covers creation rules, error conditions, follow-up actions, and return values. The existence of an output schema reduces the need to describe the full response shape.

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 coverage is 80%, and the description adds significant meaning to the kind and model_ids parameters: it explains valid values, semantics, seeding rules, and constraints. However, server_version is undocumented in both the schema and the description, so the description does not fully cover every parameter.

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 clearly states the tool creates a group, specifies the two kinds (tag and system), and describes what each kind means. It distinguishes this creation tool from related operations like add_model_to_group by explaining seeding and post-creation member addition.

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 explicit when-to-use guidance by separating tag versus system behavior, states that system groups cannot be seeded at creation, and directs users to add_model_to_group for adding members later. This gives an agent a clear decision path.

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