suverse_balance

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

No annotations are provided, so the description carries the behavioral disclosure burden. It states this is a read operation and discloses that the wallet is 'configured' (not user-specified) and that the call is free. This adds meaningful context beyond a simple 'read balance' statement, though it does not detail response format or error behavior.

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?

The description is a single, front-loaded sentence with no filler. Every phrase contributes: the resource, the action, the additional output, and the free-to-use note. Highly concise and well-structured.

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 zero-parameter, read-only utility, the description is complete. It specifies the balance source and the call-remaining information. No output schema exists, so the description partially covers return values by stating 'how many calls remain for each tool'. Minor gaps: it doesn't specify the response structure or whether the balance is in decimal units, but overall it is sufficient.

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 tool has zero parameters, and the schema coverage is 100% (empty schema). The description adds meaning by clarifying what data is read (on-chain USDC balance for the configured Base wallet) and the output includes call counts per tool. With no parameters to explain, the baseline of 4 applies.

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 function with a specific verb ('Read') and names the exact resource ('configured Base wallet's on-chain USDC balance') and the additional output ('how many calls remain for each tool'). It distinguishes itself from sibling suverse_* tools by focusing on balance and call quotas.

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 makes the intended use obvious: check USDC balance and remaining calls. It indicates the tool is free to use ('FREE — no payment'), which is a clear usage context. However, it does not explicitly compare to alternative suverse tools or provide when-not-to-use guidance.

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