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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the description's 'WRITE:' prefix largely restates the mutation behavior. It adds some value by naming the underlying endpoint (POST /api/groups), but says nothing about failure modes such as duplicate names, required permissions, or whether the new group is returned.

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 terse fragments that front-load the write intent and the resource, with zero filler. The endpoint reference is mildly redundant for an agent but not wasteful; the only criticism is extreme brevity rather than verbosity.

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 seven-parameter creation tool with no output schema, the description conveys the core action but omits what the agent gets back, such as the new group's identifier, and offers no guidance on validation or duplicate handling. It is adequate for calling the tool but not for interpreting the result.

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% and each of the seven properties carries its own description with constraints such as color patterns and 0-means-no-limit semantics, so the schema does the heavy lifting. The description adds no additional parameter meaning, which makes the baseline 3 correct.

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 uses the specific verb 'add' with the resource 'resource group', making the create semantics unambiguous and contrasting implicitly with the sibling update_group. It stops short of naming siblings explicitly, but an agent can readily distinguish it from get_group, list_groups, and 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 'WRITE: add a new resource group' phrasing implies this is the creation path, which is useful context, but the description never states when to prefer it over update_group or what prerequisites apply, such as whether the group name must be unique. The usage guidance is inferable rather than explicit.

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