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

The 'confirm-gated: previews until confirm: true' note is genuinely valuable beyond annotations: it tells the agent that a call without confirm performs no mutation and returns a preview, which prevents accidental writes. readOnlyHint=false is consistent with a mutation. It stops short of stating whether omitted fields are left untouched, permission requirements, or what the preview contains.

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 short sentences with the mutable scope front-loaded and the critical confirm-gating caveat in a compact parenthetical. No filler, nothing repeated from the schema.

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 nested-input mutation tool with no output schema, the description covers the essentials: what changes, and that nothing happens without confirm. Missing is whether this is a partial patch (unmentioned fields preserved) and what the preview returns, which matters since there is no output schema to explain the response.

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 only 33%, so the description must compensate; it does name all three mutable nested fields (name, color, description), mapping them to the input object. But it adds no format or constraint detail (60-char name cap, hex color pattern, 300-char description) and says nothing about the required `id` parameter or which group it identifies.

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?

Names a precise verb set (rename, recolour, change description) against a specific resource (a client group), which immediately separates it from create_client_group, delete_client_group, add_group_members, and get_client_group. The scope of what can be changed is stated outright rather than left to the schema.

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 confirm-gate parenthetical implies this is a deliberate two-step operation, so usage context is partially conveyed. However, it never states when to prefer this over siblings (e.g. create_client_group for new groups, add_group_members for membership), nor any prerequisite like needing an existing group id.

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