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

Goes well past the annotations (readOnly/idempotent/non-destructive/openWorld) by disclosing that no server-side mint secret exists, that a mint keypair must be generated client-side, that Pump.fun fee-share may be one v0 tx or an ordered pair, that all steps must be signed in one signAllTransactions or Jito bundle, and which env keys each platform requires. The fee map and treasuryBps range further clarify behavior an agent could not infer.

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?

Almost every clause carries real information, but it is delivered as one dense run-on paragraph with the purpose buried after two sentences of fee economics. Reordering purpose first and grouping platform/param rules would improve scanability without losing content.

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 19-parameter, no-output-schema tool, the workflow (build unsigned -> sign all steps -> submit) and per-platform auth requirements are covered, which is the critical path. Gaps remain around several parameters (mode, seats, initialBuySol) and the shape/ordering of the returned transaction steps, which matters given the 'ordered pair' fallback.

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 only 26%, and the description compensates for the highest-value params: platform (all six enum members with venue/chain and env requirements), mintPubkey, crew[] sourcing, treasuryBps range, and optInOnly default. However mode, seats, initialBuySol, name, ticker, twitter, website, imageUrl, imageBase64, description, and launcherPubkey remain unexplained in both places.

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 states a specific verb and resource ('Create UNSIGNED launch transactions'), and the 'UNSIGNED' qualifier implicitly separates it from signing/submitting siblings like crew_submit_signed and crew_launch. It never names those alternatives outright, and the economic preamble ('earns 15% of creator fees') delays the actual purpose to the third sentence.

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?

Strong contextual rules: mintPubkey is required for Pump.fun, every returned step must be signed together, the lock step must not be skipped, crew_wire_fees is repair-only, explicit crew[] from crew_list_kols is preferred over Autohire, and optInOnly defaults off. It stops short of explicitly stating when to choose this over crew_launch or crew_submit_signed, so the core routing decision is inferred rather than stated.

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