get_agent_balance

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

Discloses read-only nature, no cost (no x402, no credits), and no side effects. Since no annotations exist, description fully bears behavioral disclosure and does so comprehensively.

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?

Description is compact but well-structured with sections (USE WHEN, NOT WHEN, RETURNS). Every sentence provides essential information, no fluff.

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?

Despite no output schema, the description details return fields (pending_ndat, claimed_ndat, total_earned_ndat). Covers usage context, cost, side effects, and parameter constraints fully for a simple 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?

Schema coverage is 100% with a description for 'wallet'. The description adds format specifications (0x + 40 hex chars, optional checksum) that enhance understanding beyond the schema. Baseline 3, but value added justifies 4.

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?

Clearly states the tool checks pending and claimed NDAT swap-reward balance for one agent wallet on Base. Specific verb (check), resource (balance), and constraints (Base, NDAT swap-reward) make purpose unambiguous and distinct from sibling tools.

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 (after register_nattswap_reward or before claim_ndat) and when not to use (for quota credits or BTC signals), referencing alternatives. Provides clear context for tool selection.

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