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

Annotations already declare destructive=true, idempotent=true, readOnly=false, so the safety profile is known. The description adds real value beyond that: the code is auto-created if missing, the move is not a copy (no double-counting, no unmapped categories), and the same call reverses it — all useful operational context not present in annotations.

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 front-loaded sentences lead with the action, then explain the move-not-copy semantics and reversibility. Slightly rhetorically worded ('nothing is ever counted twice'), but every clause earns its place and nothing is redundant.

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?

With an output schema present, return values need not be explained. The description covers the key gaps for a destructive mutation: auto-creation of the target code, atomic move semantics, and reversibility via the same tool. What is missing is explicit routing relative to sibling chart tools.

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%, so all three parameters are already documented in the schema, including the enum and the label-only-on-create nuance. The description adds no parameter-level detail beyond the schema, 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 ('roll up'/'moves') and resource ('a spending category' onto 'a different code in the chart'), plus the side effect of creating the code. This clearly distinguishes it from siblings like rename_chart_account or chart_of_accounts, which do not move categories between codes.

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?

It implies when the tool is useful (moving a category to a different code, and reversing with the same call), but never names an alternative or states an explicit when-not-to-use condition relative to siblings such as rename_chart_account. Usage context is implied rather than spelled out.

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