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

With no annotations, the description carries the full burden and does well: it discloses the auth scope (finance:write), the default error path when force is omitted, and that dissolving the group keeps the transactions. It leaves some side-effect detail unstated (e.g. whether the removed transactions persist independently in the ledger).

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?

Three short sentences, front-loaded with the core action, then the force rule, then the scope requirement. Every sentence carries information an agent needs.

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 mutation tool with no annotations and no output schema, the description covers the key behaviors: conditional dissolution, the error path, and the required permission. It stops short of stating whether removal itself is reversible or whether transactions persist outside 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 description coverage is 100% and the force parameter is already well documented inline. The description adds only one nuance beyond the schema ('transactions are kept'), so the 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: 'Remove transactions from a group.' The operation is unambiguous and clearly distinguishable from the add_transactions_to_group and remove_transactions_from_budget siblings without opening any 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 a concrete conditional: pass force=true when the removal would leave fewer than 2 transactions, otherwise the call errors. It also names the required finance:write scope. It does not explicitly contrast with alternatives like delete_transaction_group, so a 4 rather than a 5.

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