Permanently remove a financial account from Firefly III by providing its ID. Eliminates unwanted or obsolete accounts to keep your personal finance data accurate and clean.
Permanently delete an account.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses permanence, which is useful, but it does not mention whether deletion cascades to related data (e.g., transactions, budgets), requires confirmation, or is irreversible beyond the word 'permanently'. For a destructive operation, this is a significant gap.
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 a single, efficient sentence with no wasted words. It is appropriately sized for a simple tool, though it could earn a 5 by adding a brief usage note.
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 destructive tool with no annotations and no output schema, the description is too thin. It lacks information about cascading effects, required permissions, and what happens to associated data. An agent cannot fully assess the consequences of invoking this tool.
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 0%, and the description adds no meaning to the 'id' parameter beyond what the schema shows. The agent only knows it is a string identifier; the description does not clarify what kind of ID (account ID, numeric vs. UUID) or how to obtain it.
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 states a specific verb ('delete') and resource ('account'), and the word 'permanently' adds important scope. It is clear what the tool does, though it doesn't explicitly distinguish it from sibling delete tools beyond the resource name.
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?
No guidance on when to use this tool versus alternatives like update_account or delete_transaction. The context implies it is for removing an account, but there is no mention of prerequisites, side effects, or when deletion is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.