channel_balance

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

No annotations are provided, so the description must convey the operation's nature. 'Check' clearly implies a read-only query and the enumeration of balance, spend, and request count explains what state is being inspected. It does not fully detail error behavior or auth failure cases, but the core behavioral character is transparent.

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?

A single concise sentence with no filler. It front-loads the action and resource, then lists the key outputs. Every word contributes meaning.

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 simple tool with one optional param, no output schema, and no annotations, the description adequately defines what the tool does and what it reports. It would benefit from a brief note on when to use it relative to open_channel, but nothing critical is missing for direct invocation.

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 100% and the single optional apiKey parameter is already documented in the schema with format 'channelId:channelSecret' and fallback to BSVKEY_API_KEY. The description adds no additional parameter meaning beyond what the schema already provides.

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 uses a specific verb ('Check') with a clear resource ('a prepaid channel') and enumerates the exact data returned (remaining BSV balance, spend, and request count). This is easily distinguished from sibling tools like open_channel or infer.

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 implies this should be used when you need a channel's balance/usage stats, but it does not explicitly state when to use it versus alternatives, nor does it mention any exclusions or preconditions such as the channel needing to be already open.

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