quote_mint

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

With no annotations, the description does a good job stating it has no side effects (no transaction) and discloses the return values (price, total, window, limit). It could mention potential error cases but is sufficient for a read-only quote.

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 sentences efficiently convey all necessary information: what it does, its side-effect-free nature, and its purpose. No unnecessary words, front-loaded with key action.

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 no output schema, the description fully explains the output: per-cell price, total for given quantity, drop window, and per-wallet limit. Single parameter is well-defined. All needed context for an agent to use the tool correctly is present.

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% and already describes the 'quantity' parameter. The description repeats the meaning (number of land cells) and adds context about per-cell price and total, but does not add significant new semantic information beyond the schema.

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 it previews a primary-market land mint, reads live SeaDrop data, and returns price and window info. It distinguishes itself from the sibling 'mint_cell' which commits the mint.

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?

Explicitly says to use it before 'mint_cell' to size the buy and confirm the drop is active, and notes it has no side effects. This provides clear when-to-use and when-not-to-use guidance.

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