update_account

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

No annotations are provided, so the description must carry the full burden. It only lists a few possible updates (rename, toggle net worth, hide) without disclosing side effects, permissions, reversibility, or partial-update behavior. The schema reveals additional behaviors like display_balance and hide_transactions_from_reports that the description omits.

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?

A single sentence with no filler, front-loaded with the primary action. It communicates the key capabilities in minimal space.

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 six parameters, no annotations, and no output schema, this is a complex update tool that deserves more detail. The description under-specifies the full scope of updates and fails to mention several modifiable fields, making it incomplete for an agent to understand the tool's full impact.

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 description adds meaning for include_in_net_worth ('toggle net worth inclusion') and hide_from_list ('hide it'), which partially compensates for the 50% schema coverage. However, display_balance and hide_transactions_from_reports remain undescribed in both schema and description, so the compensation is incomplete.

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 clearly states the tool's actions: renaming an account, toggling net worth inclusion, and hiding it. This distinguishes it from sibling tools like delete_account and get_accounts, and uses specific verbs tied to a resource.

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 usage is implied: this is an update tool for accounts, but no explicit guidance is given about when to prefer it over alternatives like delete_account or refresh_accounts. The context signals list siblings but the description omits any direct comparison or exclusions.

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