magicblock isMintInitialized

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

The description says 'Check' implying a read operation, but annotations have readOnlyHint=false, contradicting that implication. This is a serious inconsistency that misleads the agent. No mention of side effects, state changes, or behavior beyond the check.

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 very short, consisting of one sentence plus a price. It is front-loaded with the core purpose. However, it omits important behavioral details, so brevity comes at the cost of completeness.

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 contradiction with annotations and lack of usage guidelines, the description is incomplete. It does not explain the output or how the check result is returned, though an output schema exists. The tool's behavior is not fully specified.

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?

All three parameters have descriptions in the schema (100% coverage), so the description adds no extra semantic value beyond what is already structured. The price note is irrelevant to parameters. Baseline score of 3 applies.

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 specifies the tool checks whether a mint has a validator-scoped transfer queue on the ephemeral RPC. The verb 'Check' and specific resource 'mint with transfer queue' clearly state the purpose, distinguishing it from other magicblock tools like magicblock_initializeMint or magicblock_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?

No guidance on when to use this tool versus alternatives such as magicblock_getAccountInfo. There is no discussion of prerequisites, context, or when not to use it. The description simply states what it does without usage recommendations.

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