quote_buy

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

With no annotations provided, the description carries full burden. It clearly states the tool is non-destructive and reserves nothing, and notes it requires a session. This is sufficient for a preview tool, though it could mention any rate limits or auth requirements.

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 three sentences, front-loaded with purpose, and each sentence serves a distinct role: define purpose, explain key parameter behavior, and advise on usage order. No wasted words.

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?

The tool is a simple preview with no output schema. The description covers the main use case and parameter semantics. It doesn't explain return values, but for a cost preview, the return is likely obvious. Minor gap but overall complete for its 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%, but the description adds meaningful context beyond the schema: it explains the `chain` parameter's impact on the estimate type (with or without transit fees) and clarifies that the schema's description is essentially the same. This adds value for the agent.

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 the specific verb 'Preview' and resource 'cost of buying from a lot', immediately clarifying the tool's function. It also distinguishes from sibling tool `buy_lot` by stating it is non-destructive and reserves nothing.

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 explicitly tells when to use this tool ('Use this before buy_lot') and explains the two modes for the `chain` parameter (include for exact total, omit for seller-only estimate). This provides clear context for when to use each variant.

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