request_import_quote

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

Discloses that submitting shares contact details per privacy policy, and reinforces consent meaning. With no annotations, description carries full burden and covers key behavioral traits of data sharing.

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?

Three sentences, no fluff. Front-loaded with the main purpose, then usage conditions, then data handling note. Every sentence earns its place.

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?

Provides enough context for an agent to decide when and how to invoke, given no output schema and well-documented parameters. Could mention post-submission behavior but still complete.

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?

Adds value beyond schema by explaining the consent condition ('set true ONLY if explicitly agreed'), the phone/email requirement, and the source (German/EU auctions). Schema coverage is 100% so baseline 3, but adds meaningful context.

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 the tool asks Clara Carros to source and quote a specific car for import from German/EU auctions, distinguishing it from sibling tools like search_inventory or calculate_isv.

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 specifies when to call: when user wants an import quote and provides model, name, phone/email, and explicitly agrees to be contacted. Includes condition for consent parameter, leaving no ambiguity.

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