Meteora Create D L M M Pool

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

Annotations indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, which tells the agent this is a write operation with side effects. The description adds no additional behavioral context (e.g., that it requires SOL for transaction fees, that creating a duplicate pool will fail, or what the output contains).

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 concise, consisting of two sentences. The first sentence clearly states the tool's primary action. The second sentence provides context about SAP tools, which may be relevant but somewhat tangential. Every sentence has a purpose, though the second could be more focused on DLMM pool creation.

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 tool's complexity (11 parameters, 5 required), the description is minimal. It does not explain parameter interdependencies, typical values, or what the output schema contains (though output schema exists). The SAP context is included but does not enhance understanding of DLMM pool creation. The tool has a rich schema and annotations, so the description could do more to guide the agent.

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?

Input schema coverage is 100%, so the schema already describes all 11 parameters. The description does not add any extra meaning or usage hints for parameters like binStep, initialPrice, activationType, etc. Baseline score of 3 is appropriate as per rubric.

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 'Create a Meteora DLMM (Discrete Liquidity Market Maker) pool,' which is a specific verb and resource. The title and name further clarify the purpose. It is distinct from sibling tools like meteora_addDLMMLiquidity and meteora_createDynamicPool.

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?

The description includes SAP MCP context and suggests using SAP tools for on-chain registration, but provides no guidance on when to use this tool versus other Meteora pool creation tools (e.g., meteora_createDynamicPool, meteora_createAlphaVault). No criteria for selecting this tool over alternatives are given.

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