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

Annotation contradiction: description says 'Read' implying read-only, but readOnlyHint is false. This inconsistency undermines trust. The description adds no behavioral detail beyond the contradictory hint, and the SAP guidance is generic boilerplate.

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?

First sentence is clear and concise, but followed by a long block of SAP execution guidance that is repetitive and not tool-specific. Could be trimmed to improve readability.

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 are covered elsewhere. Description covers basic purpose, auth requirement, and payment flow. However, the annotation contradiction and lack of explanation about 'ephemeral-rollup' leave some gaps.

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% with individual parameter descriptions. The description adds no extra semantic detail beyond noting authToken requirement, which is already in schema. Adequate but no value added.

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 context 'requires bearer token from login'. This distinguishes it from sibling 'magicblock_balance' which likely does not require auth.

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 implies prerequisite (call magicblock_login first) and indicates a paid read workflow via SAP execution guidance. However, it does not explicitly contrast with the non-private sibling or state when NOT to use this tool.

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