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

Discloses quote expiration (not in annotations) and that execution requires a signing key. Annotations already indicate readOnlyHint=true and openWorldHint=true; description adds valuable behavioral context without contradiction.

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?

Three sentences with no waste. Front-loaded with the core purpose and immediately useful details (expiration, security). Every sentence earns its place.

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?

Covers what the quote provides (arrival amount, fee breakdown, balance check) and expiration. No output schema exists, but description gives sufficient context for agent decision. Could be more explicit about return format.

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 has 100% coverage; description does not add meaning beyond schema. It contextualizes parameters within the overall purpose but doesn't explain format or constraints.

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 tool's purpose: 'Price out emptying a chain's native gas balance to exactly zero,' specifying the action (price out), resource (native gas balance), and outcome (quote ID). It distinguishes from siblings like zerodust_get_balances by focusing on sweep quoting.

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 tells when to use this tool (to get a quote) and when to use something else (the SDK for execution). Also mentions quote expiration (60 seconds) and security constraint (hosted server doesn't hold signing key).

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