ab_agw_create_wallet

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

Annotations provide destructiveHint=true, indicating this is a write operation. The description adds valuable context beyond annotations: it specifies that the tool wraps an external helper ('@abstract-foundation/agw-client’s deployAccount'), describes the return values (address and tx hash), and notes that the tx hash may be 'undefined' if the account already exists. This enhances understanding of the tool's behavior without contradicting annotations.

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 front-loaded with the core purpose in the first sentence, followed by implementation details and return values in subsequent sentences. Each sentence adds value without redundancy, making it efficient and well-structured for quick comprehension.

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 the tool's complexity (deploying a smart-contract with destructive hint) and lack of output schema, the description provides good coverage: it explains the action, underlying helper, and return values. However, it could benefit from more details on error conditions or deployment prerequisites to be fully complete for a destructive operation.

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?

With 100% schema description coverage, the schema fully documents the single parameter 'signer'. The description adds marginal value by reinforcing the parameter's role ('for a given signer') and implying its optional nature, but doesn't provide additional syntax or format details. Since there's only one parameter, the baseline is high, and the description adequately complements the schema.

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 specific action ('Deploy a new Abstract Global Wallet') and resource ('smart-contract account') with the target ('for a given signer'). It distinguishes from sibling tools like 'ab_generate_wallet' by specifying this creates a smart-contract account rather than a regular wallet, and from 'ab_deploy_token_erc20' by focusing on wallet deployment versus token deployment.

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 implies usage when needing a smart-contract account for a signer, but doesn't explicitly state when to use this tool versus alternatives like 'ab_generate_wallet' for non-smart wallets or other deployment tools. No explicit exclusions or prerequisites are mentioned, leaving some ambiguity about the decision context.

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