raydium-pools_createCLMM

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

No annotations are provided, and the description does not disclose any behavioral traits beyond creation. It fails to mention on-chain effects, transaction costs, permissions, or idempotency, leaving the agent without critical behavioral context.

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 a single, clear sentence with no extraneous information. It is appropriately front-loaded, though it sacrifices completeness for brevity.

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?

Given the complexity (10 parameters, no output schema), the description is severely lacking. It does not explain what the tool returns, how to interpret success, or any broader context about CLMM pools. The tool-level information is insufficient for confident selection.

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 high (90%), so the schema already provides good parameter descriptions. The description adds minimal value by referencing 'price range' in connection with priceLower and priceUpper, but it does not supplement the missing startTime description.

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 clearly states the action ('Create'), the specific resource ('Raydium CLMM pool'), and a key feature ('with a price range'). It distinguishes from sibling tools like createAMMv4 and createCPMM by naming the pool type, though it could be more explicit about differences.

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?

No guidance on when to use this tool versus other pool creation tools (AMMv4, CPMM) or prerequisites (e.g., token existence, SOL for rent). The description lacks any context on appropriate usage scenarios.

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