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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds material context beyond them: the settlement precondition, the post-archive state (readable but rejects new expenses), and the human-confirmation requirement. Those are exactly the details an agent needs to avoid a premature irreversible call.

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 and effect, then the precondition, then the confirmation gate. No filler or repeated information.

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 two-parameter mutation with an output schema, the description covers everything that matters: preconditions, irreversibility/reversibility of effects, and required human sign-off. Return values are handled by the output schema, so nothing essential 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 50%: idempotency_key is fully documented in the schema, while group_id has only a UUID format/pattern. The description adds no parameter-level detail (e.g. that group_id must reference a group the caller can administer). Baseline 3 is appropriate since the schema carries most of the load and UUID identifiers are largely self-describing.

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 and resource plus scope: 'Close a group for good.' Combined with the consequences for archived groups, an agent can distinguish this from leave_group, update_group, and sibling group tools without opening 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?

Gives an explicit precondition (every member settled, all balances zero, no pending payments) and an operational gate ('Confirm with your human first'). It stops short of naming alternatives such as leave_group or update_group, which would make the routing guidance complete.

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