read_obd2_pids

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

No annotations provided, so description carries full burden. It states it queries and returns decoded values, but does not disclose if it is read-only, if it requires a connection, or if it blocks. Lacks information about potential latency or empty results.

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?

Single sentence with clear verb and examples. No redundancy. Front-loaded with key action.

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?

For a no-parameter tool with minimal complexity, description covers purpose and return type. Lacks prerequisites but overall adequate. Output schema not provided, so no need to cover return structure.

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?

No parameters in schema, coverage 100%. Baseline is 3 per guidelines. Description adds no parameter-specific info beyond schema, but no parameters exist to explain.

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 queries all known OBD2 PIDs and returns decoded physical values. Lists examples like RPM, speed, throttle. Distinguishes from sibling 'query_obd2_pid' which queries a single PID.

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 guidance on when to use this tool versus alternatives like 'query_obd2_pid' or 'check_obd2_support'. No mention of prerequisites such as needing a prior connection.

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