deleteAccount

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

With no annotations, the description must disclose behavioral traits, but it only says 'delete'. It does not mention irreversibility, potential side effects on transactions/balances, or required permissions. This leaves significant behavioral uncertainty for a destructive 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 a single, short, front-loaded phrase with no filler words. It efficiently conveys the core purpose without wasting tokens.

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?

Although the tool is simple and has an output schema, the description fails to address crucial context for a deletion operation: what happens to related data, whether the action is reversible, and error conditions. This incompleteness is risky for an autonomous agent.

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 has one 'id' parameter with 0% description coverage, but the description links it to a bank account, giving some context. It does not add details like 'the id of the account to delete', but for a single 'id' field this is minimally adequate.

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 'Excluir conta bancária' (Delete bank account) provides a specific verb and resource, clearly distinguishing it from sibling delete tools like deleteCreditCard, deleteCategory, and deleteTransaction. It leaves no doubt about the tool's purpose.

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 no guidance on when to use this tool, prerequisites, or alternatives. It merely states the action without explaining conditions or exceptions, so the agent gets no help in selecting this over other delete tools.

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