update_wallet

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

The description only says 'Update' with no disclosure of behavioral traits such as side effects, permissions required, reversibility, or behavior on partial updates. With no annotations, this is insufficient.

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 concise sentence. However, it is too minimal for a tool with complex parameters, lacking essential details. It is not verbose but under-specified for the complexity.

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?

The description is incomplete given the tool's complexity (two parameters, one being an open object). It does not explain return values despite an output schema existing, nor does it cover the behavior of the 'updates' parameter.

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 0% (no parameter descriptions in the schema). The description does not add any meaning to the parameters 'wallet_id' or 'updates', leaving the agent to infer their purpose and structure from names alone.

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 action ('Update') and the resource ('wallet metadata and configuration'). It distinguishes from siblings as the only update tool among similar tools like create_wallet, get_wallet, list_wallets, etc.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use, or comparison with other tools like create_wallet or get_wallet.

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