Explain how a native gas balance can be emptied to exactly zero, what it costs, and how to integrate. Call this when asked how ZeroDust works, why a full balance normally cannot be sent, or what sweeping will cost.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds that it explains costs and integration, which is beneficial context beyond the annotation.
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 sentences, front-loaded with purpose and usage. Every word earns its place; no redundancy or unnecessary detail.
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 no input parameters and no output schema, the description fully covers what the tool does and when to use it. It is complete for an informational tool.
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?
No parameters exist, and schema coverage is 100%. The description does not need to add parameter details, so baseline 4 is appropriate.
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 it explains how to empty a native gas balance to zero, including costs and integration. It distinguishes itself from sibling tools that perform specific actions (e.g., get balances, get quotes) by being purely informational.
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?
Explicitly specifies when to call: when asked how ZeroDust works, why a full balance cannot be sent, or what sweeping will cost. Provides clear context for use without ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose: finding balances, listing chains, quoting sweeps, checking status, explaining concepts, listing history, and registering API keys. No overlap or ambiguity.
Most tools follow a consistent 'zerodust_verb_noun' pattern (e.g., get_balances, list_sweeps). 'info' is a slight deviation (single verb instead of verb_noun), but it's minor and still clear.
7 tools are well-scoped for the focused domain of recovering stranded gas tokens. Each tool serves a necessary function without redundancy.
Covers core workflows: discovery, pricing, status tracking, history, and explanation. The actual sweep execution requires a signing key, which is intentionally excluded from the hosted server (handled via SDK). Minor gap: no cancel/abort tool.