Delete Fortnox Account

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

Annotations already mark destructiveHint=true, but the description adds crucial details: 'cannot be undone' and 'must not have any transactions.' It also states a return confirmation, adding beyond 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?

Five short lines: action, warning, precondition, arg doc, return. Front-loaded and 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?

For a one-parameter destructive delete, it includes warning, precondition, and return value. Output schema is absent but return is stated. It could specify error behavior (e.g., if account has transactions), but the warning implies it won't proceed.

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 coverage is 100% with account_number defined and constrained (integer 1000-9999). The description repeats the parameter name/type but adds no new semantic details beyond the schema.

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?

Description clearly states 'Delete an account from the chart of accounts,' specifying the verb and resource. It distinguishes from sibling delete tools (e.g., delete_customer, delete_supplier) by targeting 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 warns that the account must not have any transactions, providing a clear precondition for use. It also flags irreversibility. While it doesn't explicitly name alternatives, the precondition serves as a when-not condition.

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