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

With no annotations provided, the description carries the full disclosure burden and meets it thoroughly: it reveals the decode-and-diff behavior, enumerates the validation surface (GlobalConfig, platform id per mode, curve, supply, totalSellA, raise, Token-2022 base mint, quote token program, curve-rule account last, reward-mode transfer fee), states the return shape (ok, mismatches with fixes, warnings), and adds a safety guarantee ('A mismatched pool is never adopted: the tax goes to nobody'). This goes well beyond what a typical description provides.

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 front-loaded with the most decision-critical information ('Call BEFORE broadcasting'), followed by inputs, behavior, and consequences in logical order. Though it contains a long field enumeration, every item is decision-relevant specificity rather than filler; the 'maxinumFee' typo detail earns its place by warning the agent about a real field name. No sentence is wasted.

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?

This is a complex, multi-parameter validation tool with no output schema, so the description must explain return values — and it does ('Returns ok, mismatches with fixes, warnings'). It also covers when to call it, what to pass, what is checked, and the failure consequence (mismatched pool never adopted). Nothing an agent needs to invoke and interpret it correctly is missing.

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%, so the baseline is 3. The description adds value on top: it ties each parameter to the diff behavior ('Pass the base64 unsigned transaction, the quote mint, and the mode'), and it concretizes the launch_params linting with real examples (Raydium's transferFeeBasePoints / 'maxinumFee' spelling), which the schema only gestures at ('linted for misspelled fee fields'). That is meaningfully beyond the schema, earning a 4.

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 precise verb-resource pair: it decodes a LaunchLab initialize instruction and diffs it against StonkFun's /launchlab/pricing. It names the exact inputs, the exact fields checked, and the outputs (ok, mismatches with fixes, warnings). The 'Call BEFORE broadcasting' scoping and the specific /launchlab/pricing reference cleanly separate it from all stonk_* siblings (stonk_pairs, stonk_screener, stonk_yield), none of which do preflight validation.

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?

'Call BEFORE broadcasting a self-built Raydium LaunchLab launch meant for StonkFun' is an explicit, time-bound usage directive that also scopes the tool to self-built launches and rules out non-StonkFun contexts. It does not name alternatives or state when-not-to-use, but no sibling tool competes for this job, so exclusions would be low-value. This is clear context without explicit exclusions, fitting the 4-level.

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