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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety bar is lower. The description still adds real value the annotations cannot convey: no confirmation prompt ('runs without asking first'), no member notifications, and the return shape ('returns the whole new list'). It does not, however, warn about the destructive/overwrite implications the annotation implies.

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?

Four short sentences, front-loaded with the action, then permission, then update semantics, then side effects. Every clause carries information; nothing is padded.

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?

With no output schema, the description compensates by describing the return ('the whole new list'), and it covers permissions, partial-edit behavior, and notification side effects. Only the destructive/overwrite risk implied by destructiveHint is left unaddressed.

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 100%, so baseline would be 3. The phrase 'fields you leave out stay' adds genuine PATCH-style semantics not expressed in the schema — an agent learns that omitting title or description preserves the existing value rather than clearing it. 'Rule number from list_group_rules' is also mirrored usefully in the description's context.

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?

States a specific verb ('Change') and resource ('title or text of a group rule') and makes clear it edits exactly one rule, which separates it from add_group_rule/delete_group_rule. It never names a sibling explicitly, so it stops short of a 5.

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?

'Admins only' gives a hard prerequisite, and 'Edits one rule, as Settings, Rules, Edit does: fields you leave out stay' tells the agent this is a partial update. It lacks explicit when-not-to-use guidance or a named alternative tool, so it is clear context rather than full routing.

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