Editar Conta

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

Annotations already provide destructiveHint: true, signaling mutation. Description adds that it is a write operation and requires confirm, providing extra context. However, it does not disclose any additional behavioral traits like permission needs or reversibility.

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?

Description is very short (15 words) and front-loaded with 'Operação de escrita'. No wasted words, but could be slightly expanded to improve parameter guidance without losing conciseness.

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?

Given 6 parameters, low schema coverage, and an output schema (but not shown), the description fails to explain what fields can be updated, what the tool returns, or side effects beyond the confirm flag. The description is too minimal to be contextually complete.

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 only 17% (only 'id' described). Description only explains the 'confirm' parameter (required true). Other parameters like logo, name, balance_cents, include_total_balance are left without meaning or format hints, insufficient for the low coverage.

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 'Edita uma conta manual do Despezzas' (edits a manual account), with verb 'edita' and specific resource 'conta manual', distinguishing it from create/list/delete siblings. The nature of a write operation is also stated.

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?

Description requires 'confirm: true', giving a usage condition, but does not explicitly state when to use this tool versus alternatives like creating a new account or updating other entities (e.g., credit cards). Context is implied but no when-not guidance.

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