inspect_odb

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

The description discloses that the operation is read-only, which is valuable behavioral context. However, with no annotations provided, it does not explain potential failure modes, requirements for the path, or any effects beyond opening, leaving other behavioral traits undisclosed.

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?

A single 13-word sentence that front-loads the core purpose ('Open an ODB read-only') and the expected output. 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?

For a simple two-parameter inspection tool, the description covers the essential purpose and safety. However, the lack of usage guidance and timeout semantics, combined with many sibling tools, makes it incomplete for confident selection.

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%, and the description does not explain either parameter. While odb_path is self-evident, timeout is mysterious (units, defaults, whether to pass null) and the description offers no clarification.

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 uses the specific verb 'Open' with a clear resource (ODB) and specifies the return value: metadata about steps, frames, and outputs. This is unambiguous, though it does not explicitly distinguish itself from the sibling get_odb_info.

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 when-to-use or alternative guidance is provided. An agent is left to infer that this is for inspection, but with siblings like get_odb_info and get_field_output_summary, it lacks a clear routing signal.

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