Tesla Get Odometer

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint), so the bar is lower, and the description still adds two real behavioral facts: it does not wake the vehicle, and the distance figure comes from local snapshots (implying possible staleness). It does not state how fresh those snapshots are or what happens when no snapshot exists.

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, zero filler, with the core capability stated first and the wake behavior as a secondary qualifier.

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-shape explanation is unnecessary, and the description covers both the returned metrics and the non-waking behavior. It could still note snapshot freshness or the no-snapshot fallback, but it is sufficient to 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 both vin and period are already documented, including the accepted period values. The description only echoes 'over a period' without adding format or default behavior beyond the schema, 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?

Names the specific resource returned (odometer in miles plus distance over a period), which an agent can distinguish from status/climate/software siblings. Units are given explicitly. It lacks a verb and does not explicitly contrast with the closest sibling (tesla_usage or tesla_query_history), so it stops short of a 5.

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?

'Does not wake the car' implies this is the non-intrusive read path versus tesla_wake_and_refresh, but the description never states when to choose this over tesla_get_status or tesla_usage. Usage is inferable rather than explicit.

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