Update Access Group

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds a genuine behavioral detail (the confirm=true gate), but says nothing about what state is changed, reversibility, or consequences of a bad update.

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 no padding, and the confirm requirement is front-loaded. It is efficient, though the first sentence wastes words by echoing the 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?

Given annotations that carry the destructive profile and 83% schema coverage, the description is minimally adequate for a 6-param mutation tool with nested objects. It remains thin on what the update actually affects and how payload versus body flags are meant to be used.

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 83%, so the schema already documents confirm, account, payload, payload_file, and access_group_id. The description's mention of confirm adds no meaning beyond the schema's own 'Set true only when the user asked for exactly this action,' so 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 first sentence 'Update Access Group' simply restates the title, and 'Changes community state' is a vague hint at the effect. It names the verb+resource but offers no differentiation from siblings like archive_access_group, unarchive_access_group, or create_access_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 only usage signal is 'requires confirm=true for the user-requested action,' which is a prerequisite rather than when-to-use guidance. Nothing tells the agent when to prefer this over archive_access_group, unarchive_access_group, or create_access_group.

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