Create Customer Offramp Wallet

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the description's only added behavior is 'Returns the created offramp wallet'. It says nothing about duplicate handling on retry (non-idempotent), what networks are accepted, or whether the call fails if the bank account is missing.

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?

Front-loaded one-sentence purpose followed by a short Args list and a return line. The Args block duplicates the schema and costs some space, but nothing is bloated or buried.

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?

For a mutating, non-idempotent, open-world creation call with no output schema, the description tells the agent almost nothing about the created resource (no id/status fields, no error conditions, no network constraints). It is minimally callable but not 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 description coverage is 100%, so baseline is 3. The Arg block merely restates the schema types ('customer_id (string): the customer id') without adding format, source, or constraint information (e.g. valid network values or where external_id surfaces).

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?

States a specific verb and resource: 'Create an offramp wallet' scoped to 'a customer's bank account'. That bank-account linkage distinguishes it somewhat from create_customer_wallet / create_customer_custodial_wallet, but the description never names those siblings or explains the difference explicitly.

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 indication of when to use this versus ashar_create_customer_wallet, ashar_create_customer_custodial_wallet, or ashar_create_wallet, and no preconditions such as whether the bank account must already exist or be verified before an offramp wallet can be created.

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