tesla_state_history

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

With no annotations provided, the description carries the full burden. It does not disclose side effects (none expected), authentication needs, rate limits, or data freshness. Only states what the tool shows, not behavioral traits.

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, no fluff. Front-loads the core purpose, then adds context. Every sentence 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?

Output schema exists but is not described. Description does not specify return format or fields. With one parameter left unexplained and no output description, the definition is insufficient for an agent to fully understand tool invocation and response.

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?

The only parameter (days) is not described at all in the description. Schema coverage is 0%, and the description adds no meaning beyond the schema default. Agent cannot infer valid values or behavior based on description.

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?

Description clearly states it shows vehicle state transitions (online, asleep, offline) and its relevance to vampire drain analysis. It effectively distinguishes from sibling tools like tesla_status (current state) and tesla_vampire_drain (drain analysis), though could be more explicit.

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 on when to use this tool vs alternatives. Merely mentions usefulness for vampire drain analysis, but does not state when not to use or compare with related history tools like tesla_charging_history or tesla_drives.

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