Quote a buy or sell

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

The annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context: pricing depends on whether the coin is pre- or post-graduation, and the response includes expected/minimum output, price impact, fee amount, and fee recipients.

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?

Two tight sentences: the first establishes purpose and venue behavior, the second covers side-specific inputs and return values. It is front-loaded and contains no filler.

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?

For a read-only quote tool with no output schema, the description explains the relevant return fields and platform-dependent pricing behavior. The main remaining gap is an explicit statement that this does not execute a trade, though readOnlyHint=true already signals that.

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?

The description adds side-dependent meaning beyond the schema by tying amountSol to buys and amountTokens/amountRaw to sells, including that amountTokens is in whole tokens. SlippageBps is left to the schema, which already documents its default and range, so the 67% schema coverage is reasonably supplemented.

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 uses a specific verb and resource: "Quote a trade on a justi.fun coin," and clarifies the pricing venue changes from bonding curve to Meteora DAMM v2 after graduation. It is clearly a quoting tool rather than an execution tool, though it does not explicitly name justi_build_swap as the execution sibling.

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?

It gives concrete input guidance: use amountSol for buys and amountTokens or amountRaw for sells, with whole-token semantics for amountTokens. However, it does not explicitly state when to use this instead of justi_build_swap or that it only previews a trade and does not execute it.

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