xrp_get_token_balance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation via 'Get' but does not disclose behavior like whether a trustline must exist, what happens if it does not, or any error cases. It adds no context beyond the verb and the notion of a trustline balance.

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 consists of one short sentence that directly states the tool's function. It is front-loaded with the action and resource, and there is no wasted wording.

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 read tool with three well-documented parameters, the description is minimally adequate. However, with no output schema and no annotations, it would benefit from explaining the return format or edge cases (e.g., trustline not found). It is not misleading but leaves some gap in what the agent can expect.

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 input schema has 100% coverage with descriptions for all three parameters (address, currency, issuer). The description adds no additional parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 'Get' and identifies the resource as 'custom token (trustline) balance' for an account. This clearly distinguishes it from sibling tools like xrp_get_balance (which likely retrieves XRP balance) and xrp_get_trustlines (which lists trustlines rather than a specific balance).

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 the tool is for custom token balances, but it does not explicitly state when to use this tool versus alternatives such as xrp_get_balance or xrp_get_trustlines. No exclusions or alternative recommendations are provided, so usage guidance is only implied by the wording.

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