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

The annotations already establish that the operation is destructive, non-read-only, and idempotent, so the standalone word "Destructive" adds nothing. Saying the account is removed "from the invoices" adds some scope, but the description does not clarify whether existing invoices are modified, whether the deletion is reversible, or what data remains stored.

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 action is front-loaded and the wording is easy to scan. "Destructive" is redundant with the annotations and the brevity omits useful disambiguation, but there is no substantial verbosity or structural problem.

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 three flat required parameters, full schema coverage, an output schema, and clear safety annotations, the definition is minimally sufficient to select and invoke the tool. It remains incomplete for a destructive operation because the precise invoice and account impact, recoverability, and usage alternatives are unclear.

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?

All three parameters are fully described in the schema, including company name-or-ID handling, ID discovery through list_bankverbindungen, and the requirement to repeat the ID in confirm. The description adds no parameter-specific meaning beyond that complete schema, so the baseline score 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?

The description gives a concrete verb and resource: removing a bank account from invoices, with company scope supplied by the title. It does not explicitly distinguish the operation from save_bankverbindung or other bank-account tools, and "from the invoices" leaves the exact object being deleted somewhat imprecise.

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?

There is no explicit guidance about when deletion is appropriate, when not to use it, or which sibling tool to use for listing, creating, or changing bank details. The intended use can only be inferred from the basic removal statement.

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