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

With no annotations, the description carries the full behavioral burden for a mutation, yet it says nothing about name uniqueness/idempotency, what happens when a duplicate name is submitted, required auth, or what is returned. Only the tenant-ownership scope is disclosed, leaving the error and permission surface undocumented.

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?

A single front-loaded sentence with zero filler; the creation act and its downstream purpose are both expressed without redundant restatement of the name or title.

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 2-parameter mutation with no annotations and no output schema, the description covers the intent but omits what the caller receives back -- notably the group identifier needed to reference the group in host.tool_share. It is minimally adequate rather than complete.

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%, so both `name` and `tenant_key` are already documented with their usage conditions. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 gives a specific verb+resource ("Create a named group") and scopes it to the calling tenant, which is genuinely useful. It does not, however, disambiguate itself from the close sibling host.group.add, which an agent could easily confuse with creation.

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?

It states a concrete reason to call it -- producing a group consumable by host.tool_share(visibility: "group") -- which gives the agent a clear trigger. It stops short of naming when not to use it or pointing at host.group.list/remove as the lifecycle alternatives.

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