get_car_details_batch

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

Discloses deduplication, order preservation, and sparse entries on failure. Mentions same caveats as get_car_details. No annotations provided, so description compensates well, though lacks info on permissions or rate limits.

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 compact paragraphs, front-loaded with purpose. Every sentence adds information; no 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?

Given complexity (batch), no annotations, and existing output schema, description covers return behavior and references get_car_details for caveats. Complete for an efficient batch tool.

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 100% but description adds context: ids from search_used_cars and max 50. Adds value beyond 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?

Clear verb 'get compact details' and resource 'several adverts in one call' with explicit limit of 50 ids. Distinct from sibling get_car_details by being batch-oriented.

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 positions as efficiency counterpart to get_car_details and states when to use (ranking result page). Notes deduplication and graceful failure handling.

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