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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description adds valuable behavioral context: it reads the curve on-chain (confirming read-only behavior) and discloses that sell transactions include the required ERC-20 approve. This goes beyond the annotations without contradicting them.

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 two sentences, front-loaded with the core purpose and key output detail (unsigned transactions), followed by a concise behavioral note. Every sentence earns its place with 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?

While there is no output schema, the description covers the essential return elements: the quote and the unsigned transaction(s), with a special note for sells. It does not detail the structure of the quote or the transaction format, but for this tool's complexity (5 params, no nested objects), the description gives the agent enough to invoke it correctly and interpret the high-level result.

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 description coverage is 100%, so the baseline is 3. The description adds general trade mechanics (e.g., sells include approve) but does not elaborate on parameter-specific semantics beyond what the schema already provides. It does not compensate further for any gaps, so a 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?

The description states a specific verb–resource relationship: it provides a live bonding-curve quote and unsigned buy/sell transaction(s) for a launchpad token. It also distinguishes itself from sibling quote tools like get_deadcoin_quote by scoping to launchpad tokens and by explicitly mentioning the unsigned-transaction output.

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 clearly implies when to use the tool: when the agent needs a quote or unsigned transaction for a launchpad token to sign with the user's own wallet. It does not explicitly name alternatives or state when not to use it, but the 'launchpad token' qualifier provides sufficient context to differentiate from unrelated siblings.

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