Check Driving Achievements

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-scan over recent drives, but says nothing about what an 'achievement' is, whether checking has side effects (e.g. persisting/unlocking badges), or any auth/rate-limit constraints.

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 compact sentence that front-loads the action and scope with no wasted words. It is efficient, though its brevity borders on under-specification rather than genuine conciseness.

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-value explanation is not required, and the schema fully documents inputs. Still, with no annotations and an undefined 'achievements' concept, the definition leaves the agent without enough context on the tool's behavior and scope to be fully confident.

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 100%, so both parameters (days, car_id) are fully documented in the schema, including defaults and the env fallback for car_id. The description adds no additional parameter meaning, which is the correct baseline of 3 when the schema does the work.

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 states a specific verb (scan/check) and resources (recent drives and charging sessions) tied to 'driving achievements', so the agent can tell it apart from pure data-fetch siblings like tesla_drives or tesla_charges. However, it does not distinguish itself from conceptually adjacent siblings such as check_daily_quest or get_driver_profile, and 'achievements' is left undefined.

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 when-to-use guidance, no exclusions, and no named alternative. The agent cannot tell from the text whether this is the right tool versus check_daily_quest, get_driver_profile, or tesla_driving_score; usage is only implied by the verb 'check'.

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