list_vehicles

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

Identifies external system (Shopmonkey) and filtering capability. With no annotations, carries burden for safety disclosure but omits read-only status, pagination behavior details, and default return behavior when filters are omitted.

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 efficient sentences with zero redundancy. Front-loaded action verb and clear scope.

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?

Adequate for a simple list operation with well-documented parameters. However, lacks output description (no output schema exists) and omits pagination behavior explanation despite schema including limit/page parameters.

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%, establishing baseline 3. Description mentions the two primary filter parameters (customer ID, location) but adds no semantic depth beyond schema descriptions (e.g., parameter formats, relationships to other tools).

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?

States specific verb (List) + resource (vehicles) + source system (Shopmonkey), distinguishing it from sibling get_vehicle. Could explicitly clarify 'multiple' vs 'single' retrieval.

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?

Mentions filtering by customer ID or location, implying use cases. However, fails to explicitly contrast with get_vehicle (single retrieval) or state when to use one over the other.

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