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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds genuinely new behavioral context: the atomicity requirement (sign create + fee-share lock together) and that fees lock at launch, which is exactly the irreversibility the destructiveHint implies. It stops short of describing failure/retry behavior or what a rejected submission returns.

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?

Front-loaded with the core action, then platform-specific clauses in parallel structure; nearly every clause carries operational weight. Density is high but the per-platform ordering details justify the length.

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?

For a destructive, non-idempotent submission tool with no output schema, the description covers the critical operational prerequisites and sequencing an agent needs to avoid a bad launch. It omits return/error semantics and retry guidance, which is the remaining gap.

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 0%, so the description carries the burden. It compensates well by explaining the per-platform encoding of the signed array (Solana base64 for Bags, EIP-1559 hex for Zora) and the meaning of platform ('match the builder'). It does not explain the batch constraint (minItems 1 / maxItems 8) or the minLength 64 string format.

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 (submit) and resource (signed transactions) and explicitly names the sibling that produces its input, crew_build_unsigned. An agent can distinguish it from crew_build_unsigned and crew_launch without opening either 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?

Explicitly routes the agent: call after crew_build_unsigned, pass platform to match the builder, and the pump.fun case gives a clear prohibition ('do not submit create alone'). Per-platform ordering (fee-share then create) is spelled out, leaving nothing to inference.

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