magicblock privateBalance

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

Description says 'Read' indicating read-only operation, but annotations have readOnlyHint=false, contradicting. This is a serious inconsistency. No additional behavioral context beyond contradiction.

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 a single concise sentence with key information (verb, resource, auth requirement, price). No redundancy. 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?

Output schema exists, so return values not needed. Description covers auth and cost. Lacks explanation of 'ephemeral-rollup' but sufficient for domain-aware agent.

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 description coverage is 100%. Description adds only that authToken is required, which is already in schema. No extra parameter meaning.

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 verb 'Read', resource 'ephemeral-rollup SPL token balance', and scope 'for an address'. Distinguishes from sibling 'magicblock_balance' by specifying private nature.

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?

Explicitly notes requirement of bearer token from login and cost ($0.01). Implies usage context for private balance but does not explicitly contrast with public alternative.

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