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

Annotations provide readOnlyHint=false and destructiveHint=false, and the description's 'create' action aligns with these. The description also clarifies the nature of the account (ledger vs bank), which helps set expectations. No contradictions or hidden side effects are described, which is appropriate given the simple create operation.

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 two sentences, front-loaded with the core purpose and immediately providing the key differentiation from a bank account. There is no redundant text or unnecessary detail—every sentence earns its place.

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?

The description provides sufficient context for a create operation: what it creates, what it is not, and where to go for the alternative. Since there is no output schema and the input schema is fully documented, no further context is needed at the tool level.

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 schema covers 100% of the 14 parameters with descriptive text, including examples (e.g., role: 'tax', 'taxprovision', 'salestax') and explanations of nested relationships (parentid, defaultid). Since schema coverage is high, the baseline is 3, but the parameter descriptions are detailed and add practical meaning, justifying a 4.

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 states the tool's purpose: 'Create a new chart-of-accounts ledger account' and distinguishes it from a bank account. The verb 'create' and resource 'account' are explicit, and the clarification about it not being a bank account removes ambiguity.

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 explicitly says 'Not a bank account — for that use create_bank_account,' which directly guides the user away from misuse and points to the correct sibling tool. It does not explicitly mention when to use this tool over update_account, but the creation context is clear enough for a write operation.

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