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

The description claims 'Read-only tier: this does not move funds' and implies a safe side-effect-free operation, but annotations state readOnlyHint=false, indicating the tool does write state. This is a direct contradiction. Additionally, the claim that it 'triggers the existing queued delivery' suggests it causes on-chain effects, compounding the inconsistency.

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 first sentence is tight, but the description then expands into a lengthy SAP execution guidance paragraph that duplicates text already present in the schema description. This boilerplate detracts from the tool-specific content and is not concise.

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?

While the use case and return signature are mentioned, the read-only contradiction creates confusion about the tool's actual effects. The output schema exists, so return values need not be detailed, but the misleading safety claim leaves the agent unsure whether calling this tool changes state. The boilerplate SAP guidance also obscures the relevant context.

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 provides full descriptions for all three parameters (mint, cluster, validator), so the description adds little beyond connecting 'mint' to the crank operation. The validator-scoped queue is referenced in the description, giving slight context beyond schema, but no new parameter-specific semantics are 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?

The description opens with a specific verb ('Force') and resource ('transfer queue crank for a mint'), clearly distinguishing this tool from sibling magicblock functions like transfer or swap. It also explains the intended post-private-transfer scenario, further clarifying the unique role.

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 instructs use 'after a private transfer or private swap if the Hydra delivery crank has not yet delivered funds to the recipient,' providing a concrete trigger condition. However, it does not mention when not to use or alternatives, so it stops short of full exclusion guidance.

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