tesla_trip_categoriesCount recent Tesla trips by category, optionally filtered by vehicle ID, to summarize driving activity from TeslaMate data.
Show count of trips by category for recent drives.
| Name | Required | Description | Default |
|---|---|---|---|
| car_id | No | Filter by vehicle ID (default: TESLA_CAR_ID env or first car) |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It implies a read-only aggregation but never says so, and gives no information on time window ('recent'), scoping defaults, or whether counts are per-day/per-trip.
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?
One efficient sentence with the core action front-loaded. No padding or repetition of structured fields.
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. For a zero-annotation tool the description is only minimally complete: it never defines what counts as a category or a recent drive, which an agent could need.
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 the single car_id parameter is already fully documented including its env-var default. The description contributes nothing beyond the schema, so baseline 3 is appropriate.
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 and resource: shows trip counts grouped by category, scoped to recent drives. Clear enough, though the phrase 'recent drives' is undefined and there's no explicit contrast with the close sibling tesla_trips_by_category.
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 when-to-use guidance at all. There is a directly overlapping sibling, tesla_trips_by_category, and the description gives no condition that would let an agent choose between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.