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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: this is a paid operation ($5.00 USDC) on Mainnet (real funds). It stops short of saying whether the fee is charged on failure or how retries behave despite non-idempotency.

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?

A single dense sentence with the cost front-loaded-ish and zero filler; the resource list is the only heaviness, and it maps directly to the enum. Appropriately sized for the amount of information conveyed.

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?

An output schema exists, so return values need not be described. However, for a destructive, non-idempotent, paid deployment tool whose `params` object is entirely untyped, the description omits what happens on partial failure, whether the fee is refunded, and what keys the params object expects.

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% and the contractType enum is self-documenting, so baseline 3 applies. The description's list of contract types merely mirrors the enum and adds no new meaning, and it does nothing to clarify the opaque `params` object, which is typed only as a generic object with no defined properties.

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?

States a specific verb ("initializes") plus the exact resource types (SPL Escrows, cNFT Badge Issuers, Raydium Vaults) and pinpoints the chain (Solana Mainnet), which cleanly separates it from the deploy_contract and deploy_arc_contract siblings. An agent can identify the tool without opening the schema.

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?

Usage is only implied: an agent infers this is the Solana-deployment tool and that it costs $5.00 USDC. There is no explicit when-to-use/when-not-to-use guidance, no prerequisites (wallet, funding, network config), and no routing statement pointing to the sibling deploy tools.

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