evolute_vehicles

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It discloses that VIN/IMEI are masked unless include_pii is true, which is valuable. However, it does not mention pagination, auth requirements, or any other operational behavior, leaving some gaps.

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 with no filler. The primary action is front-loaded, and the masking caveat follows naturally. Every word 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?

For a simple list tool with one optional boolean and an existing output schema, the description covers the essentials: what the tool does and the key parameter behavior. It lacks explicit scope or pagination details, but these are less critical given the output schema and simple nature of the operation.

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 0%, so the description must compensate. The masking note directly explains the effect of include_pii: setting it to true reveals VIN/IMEI. This adds essential meaning beyond the bare boolean schema, though it could have explicitly stated 'set include_pii=true'.

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 action and resource: 'List vehicles.' It also adds a relevant behavior about masking VIN/IMEI. It does not explicitly differentiate it from sibling tools, but the sibling names clearly suggest different resources, so the purpose is not ambiguous.

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?

There is no guidance on when to use this tool versus alternatives such as evolute_status or evolute_trips. The phrase 'List vehicles' implies its use, but the description provides no explicit context, exclusions, or conditions for choosing it over siblings.

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