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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes well beyond them by disclosing the hard precondition (all balances zero, no pending payments), the post-state (still readable but rejects new expenses), and an approval step before execution. This is exactly the context a destructive operation needs.

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 its finality, then preconditions, then effects, then the confirmation gate. No sentence is padding and nothing is repeated from title or annotations.

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?

An output schema exists, so return values need not be explained, and the description covers the remaining agent-relevant gaps: prerequisites, irreversible effect, retained readability, and required confirmation. Complete for a destructive, idempotent mutation.

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 thoroughly documented in the schema, while group_id is an undescribed UUID whose meaning is nonetheless self-evident from the tool name. The description adds no parameter-level detail, so the schema carries the load and 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?

States a specific verb and resource ("Close a group for good") and the permanence qualifier immediately distinguishes it from the sibling leave_group, which only removes an individual member. An agent can tell what operation this performs 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?

The preconditions are explicit and checkable: every member settled, all balances zero, no pending payments, plus a confirmation requirement. It does not, however, name alternatives or exclusions (e.g., "use leave_group if you only want to exit, or update_group to rename"), so ownership of the choice falls partly to the agent.

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