evolute_trips

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does meaningfully disclose that addresses and tracks are omitted and that distance is a raw integer with unknown units, which are valuable caveats not visible in the schema. It does not mention auth or rate limits, but for a read-like trip listing this is a strong level of transparency.

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?

The description is three concise sentences with no fluff. It front-loads the core purpose and then states two important caveats, each earning 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?

The description covers the main purpose and key output caveats, and the presence of an output schema reduces the need to describe return values. However, it does not clarify expected values for sort_by, the effect of include_pii, or pagination behavior, leaving an agent to guess for important invocation choices.

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 0%, so the description must compensate for parameter documentation. It only clarifies car_id through 'default (or given) vehicle' and says nothing about limit, offset, sort_by, sort_dir, or include_pii semantics. This is insufficient given the complete lack of schema-level descriptions.

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 identifies trips as the resource and distinguishes this from the singular evolute_trip sibling by focusing on 'Recent trips' and vehicle selection. It lacks an explicit verb like 'list' or 'retrieve,' but the intent is still readily inferable.

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?

No explicit guidance is given about when to use this tool versus alternatives like evolute_trip or evolute_vehicles. The plural 'trips' hints at a listing operation, but there is no stated condition, prerequisite, or exclusion to help the agent choose correctly.

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