Tesla Drives

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

No annotations provided, so the description must carry behavioral burden. It does not state whether this is a read-only operation, its performance characteristics, permissions, or return format (though output schema exists). Only adds minimal context about energy consumption.

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 short sentences, front-loaded with the resource. The second sentence ('Shows driving activity with energy consumption') is somewhat redundant with the first, but overall concise.

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 4-parameter query tool with full schema coverage and an output schema, the description is minimally adequate. However, it lacks usage context and behavioral disclosure, which are needed without annotations, leaving gaps for an agent to choose and invoke correctly.

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 parameter details are fully documented in the schema. The description adds nothing about parameters, but baseline is 3 when schema covers them.

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 it returns recent drives with distance, duration, efficiency, and locations, which is a specific resource and set of attributes. It distinguishes from siblings only by name; no explicit contrast with other drive-related tools like tesla_longest_trips or tesla_driving_score.

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?

Provides no when-to-use guidance or alternatives. Does not indicate when to choose this over other drive or trip tools, nor any prerequisites or time-range specifics beyond the schema.

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