Tesla Top Destinations

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

No annotations provided, so the description carries the full burden. It does not mention how visits are counted, over what timeframe, whether it reads live data, or the auth/vehicle context implied by the car_id default. Only the ranking basis is disclosed.

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?

A single front-loaded sentence with no filler. 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?

An output schema exists so return values need not be explained, and annotations are absent. What's missing is query scope (time window, visit definition) and any guidance on choosing this over the many location-related siblings.

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%, so both params (limit, car_id) are fully documented in the schema including defaults, max, and env fallback. The description adds no parameter detail, so the baseline 3 applies.

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 a specific verb (ranked) and resource (most visited locations) with the ranking metric (number of visits). Clear on its own, though it doesn't explicitly differentiate from sibling tesla_charging_by_location or tesla_location_history, which could also surface locations.

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 indication of when to use this vs. tesla_location_history, tesla_charging_by_location, or tesla_longest_trips. The agent must infer the difference between 'most visited destinations' and 'location history' on its own.

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