Read an ICRC-1 token balance on the Internet Computer

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

With no annotations, the description carries the full burden. It explicitly labels the tool as 'Read-only' and specifies it fetches data from an ICP ledger canister, which is sufficient for a read operation. No contradictions or missing critical traits (destructiveness, auth needs) are evident.

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 sentence with no wasted words. It front-loads the key action ('Chain Fusion read') and includes examples. Every part contributes to understanding.

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?

Given no output schema, the description adequately lists the return values (symbol, decimals, balance). The tool is simple with only two parameters, and the description covers the essential purpose and output. Minor omission: no mention of error states or rate limits, but acceptable for a basic read 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%, so baseline is 3. The description adds value by listing examples (ckBTC, ckETH, ICP) and clarifies the output (symbol, decimals, balance), which helps the agent understand the parameters' purpose beyond the schema descriptions.

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 fetches an ICRC-1 token's symbol, decimals, and balance from an ICP ledger canister, with examples (ckBTC, ckETH, ICP). The verb 'fetch' and resource 'ICRC-1 token balance' are specific, and the tool is distinguished from siblings like 'get_balance' by mentioning additional fields (symbol, decimals) and the 'Chain Fusion' context.

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 usage for reading token balances and metadata, but does not explicitly state when to use this tool over siblings like 'get_account' or 'get_balance'. No exclusion criteria or alternative recommendations are provided, leaving the agent to infer context.

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