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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility is largely pre-communicated; 'cannot be undone' is mostly a restatement. The one genuine addition beyond structured data is 'This affects group balances', which tells the agent the side effect reaches other members' balances — useful, but thin for a mutation with no output schema.

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 sentences, zero filler, with the action stated first and the consequence second. Every clause carries information; nothing is redundant or buried.

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 single-parameter destructive mutation, the description covers the action, the side effect (group balances), and irreversibility, and the annotations carry the safety profile. Missing only usage framing such as what state must hold before deletion, which keeps it short of a 5.

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?

Only one parameter (transactionId) exists and schema description coverage is 0%: the schema contributes a name, UUID format, and pattern but no prose. The description adds no meaning about which transaction ID is expected or what happens to an invalid/foreign-group ID, so it lands at the minimum-viable baseline for a single self-evident parameter.

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 ('Delete a group transaction') that an agent can immediately map to an operation. It does not explicitly name the sibling alternatives, but the resource noun is specific enough to distinguish it from delete_personal_transaction and the update_* variants.

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 description offers no guidance on when to use this versus update_group_transaction or delete_personal_transaction, nor any prerequisite (e.g., permissions, membership in the group). The only implied usage is 'you have a transaction ID you want gone'.

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