Meteora Create Dynamic Pool

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description correctly implies mutation. However, it adds no behavioral details such as token requirements, pool initialization effects, or idempotency. The description carries minimal value beyond the annotations.

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 first sentence is concise, but the second sentence about SAP context is irrelevant to the tool's operation and adds clutter. The description is not well-structured for an agent to quickly understand usage.

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?

Despite having 9 parameters and an output schema, the description fails to explain what a Dynamic Pool is, how to obtain parameter values, or what the return is. The SAP context sentence is extraneous and does not complete the picture. The description is incomplete for a tool of this complexity.

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 100% with each parameter already described. The description does not add any extra meaning, relationships, or usage patterns beyond the schema. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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 Dynamic AMM pool', which is a clear verb and resource, but it does not differentiate from sibling tools like meteora_createDLMMPool or meteora_createAlphaVault. The title already indicates the pool type, but the description lacks specifics on what makes 'Dynamic' distinct, leaving ambiguity.

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 provides no guidance on when to use this tool versus alternatives (e.g., when to create a Dynamic vs DLMM Pool). It does not mention prerequisites, conditions, or when-not to use. The SAP context paragraph is about unrelated tools, not usage instructions for this tool.

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