request_import_quote

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

Description discloses that the tool shares contact details per privacy policy, a key side effect. However, with no annotations, it omits other behaviors like confirmation, response format, or whether a request is immediately submitted.

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, front-loaded purpose, every sentence adds value. No fluff or redundancy.

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?

Covers main usage conditions and data sharing, but with 6 parameters and no output schema, it could mention optional budget and what the tool returns or confirms upon submission.

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 baseline applies. Description adds no extra parameter details beyond the schema; it reiterates the consent condition already in 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?

Description clearly states the tool requests an import quote for a specific car from German/EU auctions, using a specific verb ('source & quote') and distinct resource, which distinguishes it from sibling tools like get_car or search_inventory.

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 states when to call: user wants an import quote, provides model, name, phone/email, and agrees to be contacted. Also specifies consent=true only with explicit agreement. No explicit mention of alternatives, but context is clear.

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