unrugable_launch

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

Discloses key behaviors: token creation, permanently locked Uniswap V3 liquidity, reactor fee burning/compounding. Since no annotations exist, this adequately informs the agent of effects.

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?

Three sentences, front-loaded with action, no redundancy. Every sentence provides necessary information.

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?

Covers the token launch process and prerequisites adequately. Missing output details but acceptable given no output schema.

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 covers 100% of parameters with descriptions. The tool description adds no extra parameter-specific guidance beyond the overall workflow. Baseline score of 3 is appropriate.

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?

Clearly states 'Launch a new token on Unrugable' with specific verb and resource. Describes creation, liquidity pairing, and reactor wiring, distinguishing it from sibling unrugable_* tools.

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?

Lists prerequisites (GAME_WALLET_KEY and SDK) but does not explicitly state when to use this tool versus alternatives. Usage context is implied but not contrasted with siblings.

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