openf1_car_data

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable context beyond these: the ~3.7 Hz sampling rate, the high-volume warning, the top-level array return shape, and 'Auth: none needed.' This helps the agent understand scale and filtering requirements.

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?

The description is concise and front-loaded. The first sentence states the core purpose, followed by a high-volume warning and a compact return-type example. No unnecessary words or redundancy.

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?

Despite lacking an output schema, the description lists all return fields and warns about result size. It also includes auth details and suggests how to constrain results. For a read-only telemetry tool with three parameters, this is complete.

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%, with descriptions for meeting_key, session_key, and driver_number. The description reiterates that session_key and driver_number must be passed and explains the volume issue, but this largely mirrors the schema description for driver_number. It adds no new syntax or format details, 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?

The description opens with 'Car telemetry at ~3.7 Hz — speed, throttle, brake, gear, RPM, DRS,' which clearly specifies the resource and data type. This distinguishes it from sibling tools like openf1_laps or openf1_position that cover different data. The verb 'telemetry' conveys the exact nature of the output.

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?

The description provides explicit usage guidance: 'HIGH VOLUME: always pass session_key + driver_number' and advises using date>=/date<= operators to window results. This tells the agent when and how to invoke the tool, though it does not explicitly list alternatives or when not to use it.

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