magicblock privateBalance

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

The description states it is a read operation, but the annotation readOnlyHint=false contradicts this, indicating a potential inconsistency. The description itself transparently identifies the operation as a read and notes the auth requirement, but the contradiction with annotations undermines trust.

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 clear front-loading of the core purpose. However, it contains a minor typo (double period at the end), which slightly detracts from professionalism.

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 that an output schema exists, the description need not detail return values. It covers the essential action and auth requirement. However, it lacks context about what 'ephemeral-rollup' means and how to obtain the auth token (magicblock_login), which could be inferred but not explicit.

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% description coverage, so each parameter is already documented. The description adds no further semantics beyond mentioning the auth token requirement, which is already captured in the schema. It meets the baseline but adds little value.

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 'Read the ephemeral-rollup SPL token balance for an address', specifying a verb ('read') and a resource ('ephemeral-rollup SPL token balance'). It distinguishes itself from the sibling magicblock_balance by mentioning 'ephemeral-rollup', implying this is for private/rollup balances.

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 mentions that a bearer token from login is required, providing a prerequisite. However, it does not explain when to use this tool versus alternatives like magicblock_balance (presumably for public balances), nor does it offer guidance on when not to use it.

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