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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is carried there. The description adds genuinely non-obvious consequence information — that the broker accounts themselves survive the deletion — which is exactly the kind of blast-radius detail an agent needs before invoking a destructive tool.

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?

A single sentence, front-loaded with the verb and target, with the scoping clarification placed where it matters. Nothing is padded and no sentence 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 one-parameter destructive delete with no output schema and annotations covering safety and idempotency, the description covers the essentials and the key side effect. It stops short of stating failure behavior when the name does not exist or what happens to accounts currently assigned to the group.

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% for the single 'name' parameter, so the schema already documents it. The description restates that deletion is keyed by name but adds no formatting, case-sensitivity, or matching nuance beyond the schema — baseline 3.

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 description states a specific verb and resource ('Delete an account group') and immediately scopes it by name, so the operation is unambiguous. The parenthetical separates it in practice from delete_broker_account, though it does so indirectly rather than naming the sibling.

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?

Usage is only implied: 'Delete' tells the agent this is the removal counterpart to set_account_group/get_account_groups, but no when-to-use condition, prerequisites, or explicit alternative is stated. The agent must infer that a group must already exist and that this is distinct from deleting the accounts inside it.

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