decode_frame

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds 'no file is modified' which reinforces non-destructiveness and clarifies it uses a local DBC, providing useful context beyond the annotation flags.

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 sentences, front-loaded with the primary action, and no redundant phrasing or filler. Every word contributes to understanding.

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?

The tool is simple with an output schema present, so return values need not be described. Missing an explicit usage guideline is a minor gap, but overall it covers the essentials for a single-frame decoder.

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 explains data_hex as a 'hexadecimal byte string', which adds meaning. However, dbc_path and arbitration_id are left to their self-explanatory names, which is adequate but not fully developed.

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 ('Decode one CAN payload using a local DBC') with a clear resource (CAN payload) and scope (one frame). This distinguishes it from siblings like decode_log, which handles multiple frames.

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 phrase 'one CAN payload' implies single-frame use, but there is no explicit 'when to use vs alternatives' or exclusion guidance. Siblings like decode_log are not mentioned, leaving usage context implied rather than stated.

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