dbc_info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the tool summarizes a local file and returns size and node names, but it does not disclose further behavioral details like error handling or file access specifics. This is acceptable given the annotations.

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 short sentences deliver the purpose, key outputs, and a usage hint without any wasted words. The description is front-loaded with the core action and followed by usage guidance.

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 simple one-parameter tool with an output schema present, the description adequately covers what the tool does and when to use it. It does not explicitly mention alternatives, but the sibling list and 'use this first' hint provide enough context. A slightly richer description might note that validation is elsewhere, but it is not essential.

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?

The schema has one parameter with no description (coverage 0%), but the parameter name 'dbc_path' and the phrase 'local DBC file' make the meaning clear. The description does not explicitly explain the parameter format or constraints, but the path semantics are self-evident, so a 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 states a specific verb ('Summarize'), a clear resource ('local DBC file'), and specific outcomes ('size and node names'). This distinguishes it from siblings like validate_dbc (validation) and list_messages (listing messages).

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 explicitly says 'Use this first', providing clear context for when to use the tool before others. It does not mention alternatives or when not to use it, so it falls short of an explicit exclusion or alternative list.

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