clear_dtc

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states that clearing may 'reset readiness monitors' and 'temporarily turn off the MIL', and it clearly mentions the freeze-frame data is cleared. These side effects are critical for an agent to know before invoking the tool.

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 concise sentences, front-loaded with the main action and the critical approval requirement, followed by the parameter instruction and side effects. No fluff; every word earns its place.

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?

Given the tool's simplicity (one parameter), the description covers the action, the approval requirement, parameter usage, and side effects. The output schema exists, so return-value details are not required. The tool is fully understood with what's provided.

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 0%, so the description must compensate. It explicitly explains the 'confirm' parameter by instructing 'Set confirm=true', which conveys that this boolean is a safety confirmation gate. This adds meaning beyond the schema's default value and is sufficient for correct invocation.

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 states a specific action ('Clear ECU DTCs and freeze-frame') and distinguishes itself from the read-only sibling 'read_dtc' by using the verb 'clear' rather than 'read'. The resource and operation are unambiguous, leaving no room for confusion.

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 explicitly requires 'explicit user approval' and instructs the agent to 'Set confirm=true', providing a direct precondition for invoking the tool. This is clear guidance on when (and only when) the tool should be used, and it implicitly contrasts with the read-only siblings.

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