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

The description adds substantial behavioral context beyond the annotations: the account code is unchanged, the new name syncs to QuickBooks under certain conditions, existing transactions are not recategorized, the operation is audit-trailed, and actor_id attribution is constrained. This goes well beyond the readOnly/idempotent/destructive hints and does not contradict them.

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?

The description is compact and front-loaded: it states the purpose first, then key invariants, side effects, and attribution behavior. Every sentence carries meaningful operational information without redundancy.

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?

Given the complete parameter schema, the output schema, and the annotations, the description covers the important side effects, invariants, and attribution model. There is no significant missing context needed to invoke the tool correctly.

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?

The input schema already documents all five parameters with descriptions, defaults, and constraints, so the baseline is 3. The description reinforces actor_id semantics but does not add significant meaning beyond the schema's parameter descriptions.

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 clearly identifies the action ('Renames') and the resource ('a chart account'), and adds scope ('system or not') plus the key invariant that the account code never changes. This is specific enough to distinguish it from sibling tools like add_chart_account, set_chart_account_active, and list_chart_accounts.

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 gives useful context about what the rename does and does not affect, but it does not explicitly state when to choose this tool over rename-related siblings or when not to use it. The intended use is implied by the name and description rather than made explicit.

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