Src20 Balance

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

With no annotations, the description carries the behavioral disclosure burden. It usefully states that amounts are token units and that tick is optional, but it does not mention pagination behavior, address format assumptions, or confirm that this is a read-only operation beyond the word 'balances.'

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 with no filler. The main operation is front-loaded, and the decimals caveat is a valuable, compact addition.

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 read-only balance lookup with an output schema present, the description is nearly complete: it identifies the resource, optional filtering, and unit semantics. The main gap is the absence of explicit routing guidance among sibling balance tools.

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 description coverage is 0%, so the description must add meaning to parameters. It clarifies 'address' as a Bitcoin address and 'tick' as optional single-tick filtering, but it leaves 'page' and 'limit' unexplained, relying on their names and defaults.

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 identifies the resource (SRC-20 token balances) and the target (a Bitcoin address), and distinguishes all-ticks versus one-tick behavior. It lacks an explicit verb like 'returns' and does not name sibling tools, but the purpose is unambiguous.

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 intended use is implied: query SRC-20 balances for an address, optionally filtered to one tick. However, it does not explicitly compare against siblings such as src20_holders or wallet_balance, nor state when not to use this tool.

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