Deposit to Gateway

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive nature. The description adds value by noting the deposit is a one-time action that unlocks gas-free spending, and specifies the currency USDC, providing context beyond 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?

Two concise sentences front-load the purpose and benefit, with no wasted words. Every sentence adds information.

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 simple single-parameter tool with a clear output schema (though not shown), the description sufficiently covers purpose, parameter, and key behavioral outcome. No gaps.

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 for the parameter 'Amount in USDC, e.g. '5'' adds marginal value beyond the schema's description which already covers the type and format. Schema description coverage is 100%, so baseline is 3.

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 verb 'Fund' and the resource 'agent's Gateway balance', with a unique benefit 'gas-free spending afterward'. It distinguishes from siblings like pay_and_call by being about adding funds rather than spending them.

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 use for initial funding with 'once (gas-free spending afterward)', but does not explicitly compare to siblings or state when not to use. However, the purpose is straightforward and the context signals provide sibling names for reference.

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