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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further by disclosing the authorization requirement, the protected-group constraints, and the exact confirm handshake (call first without confirm, then pass confirm: true only on agreement). This is behavioral context the agent cannot get from the schema or annotations alone.

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?

Front-loads the verb and the UI mapping, then layers constraints and the confirm workflow with no filler sentences. The final confirm sentence is dense but every clause carries an instruction the agent needs, so nothing is wasted.

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 destructive, no-output-schema mutation, the definition supplies auth requirements, deletion blockers, and the confirmation flow. Nothing needed to call it safely and correctly is missing.

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 the baseline is 3, but the description adds real meaning by describing the two-step confirm protocol rather than just the parameter's literal type. It does not clarify the groupId source beyond what the schema field description ('as list_access_groups returns it') already says, keeping it from a 5.

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+resource ('Deletes a group') and immediately maps it to the concrete UI action it mirrors (Settings › Roles & access), which cleanly separates it from create_access_group, update_access_group, and delete_access_rule in the sibling set.

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?

Gives explicit prerequisites (Owner or Admin) and two explicit exclusions (the Everyone group cannot be deleted; a group a rule still names cannot be deleted until the rule is changed or removed). This tells the agent both when it will succeed and when it must redirect elsewhere.

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