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

Annotations only declare readOnly/openWorld/non-destructive, so the description earns credit for disclosing behaviors the agent cannot otherwise know: the call may wake the vehicle (a real-world side effect), it is rate-limited to one per car per 90 days, and entitlement varies by connection date. It does not say what happens when the quota is exhausted or how long the report takes.

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?

Four short sentences, front-loaded with what the report contains, then eligibility, quota, and side effect in descending importance. The pricing/grandfathering clause is verbose but is genuinely decision-relevant for the agent's user.

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?

With no output schema, the description steps in by enumerating the report's sections, and it covers cost, frequency, and the wake side effect. Only failure behavior at the 90-day limit and expected latency are left unspecified, which is minor for a read-only report tool.

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 coverage is 100% and the vin parameter already documents the multi-car requirement and the list_vehicles-first workflow, so the description correctly leaves it alone. It adds no meaning beyond the schema, which is the baseline-3 case for a fully documented single parameter.

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 names a concrete deliverable — a 'Tesla health report' — and enumerates its contents (battery estimate, tires, charge habits, alerts, software), which distinguishes it from point-specific siblings like diagnose_alerts, battery_trend, and tire_pressure_trend. The action verb is only implied by 'report', keeping it just 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?

It gives strong operational constraints — one run per car every 90 days, included in all plans, may wake the car — but never says when to prefer this over siblings such as get_vehicle_status or diagnose_alerts, nor any when-not condition. Usage is implied (a periodic full checkup rather than a targeted lookup) rather than stated.

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