magicblock balance

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

Description says 'Read' implying read-only, but annotations set readOnlyHint: false, creating a direct contradiction. This undermines trust in the tool's 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?

Description is extremely concise: one sentence plus a price note, no wasted words, and the key action is front-loaded.

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?

While output schema exists, the description omits details like return format (e.g., decimal precision) and does not differentiate from similar tools. The contradiction also reduces completeness.

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. Description does not add any additional meaning or examples for the parameters 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?

Description clearly states 'Read the base-chain SPL token balance for an address' with specific verb and resource, and distinguishes from other magicblock tools (e.g., magicblock_swap, magicblock_transfer) by focusing on reading a 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?

Description notes 'public, no auth required' and price, providing some context, but does not explicitly guide when to use this tool vs alternatives like spl-token_getBalance or magicblock_privateBalance.

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