magicblock balance

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

The description discloses that the tool is a read operation and requires no authentication, but there is a contradiction with the annotation 'readOnlyHint: false'. The description itself is clear, but the inconsistency with annotations reduces 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 that conveys the core purpose. It is concise, though there is a minor typographical error (double period at the end).

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 the tool's simplicity (read operation, 3 parameters, no nested objects, and an output schema exists), the description adequately covers the essential context. It lacks details on output format or errors, but these are partially covered by the output schema.

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 parameters are well-documented in the schema. The description adds no additional parameter details beyond what is already stated, hence a baseline score of 3.

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 reads the base-chain SPL token balance for an address, which is a specific verb+resource combination. It distinguishes itself from sibling tools like magicblock_privateBalance by specifying 'public' and 'no auth required'.

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 public balance queries by noting 'public, no auth required', but does not explicitly state when to use this tool over alternatives like magicblock_privateBalance or other balance-related tools.

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