Create DepthAI OAK pipeline

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

Annotations cover the not-read-only and not-destructive nature, and the description adds that it generates placeholders and hardware-gated notes. However, it does not disclose whether existing nodes might be modified, if a specific component selection is required, or what happens when hardware is absent.

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?

One focused sentence that front-loads the core purpose and lists key deliverables. No filler or redundancy.

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?

With 7 parameters, minimal schema descriptions, and no output schema, the tool needs richer context. The description provides only high-level scaffolding intent, not enough for an agent to confidently pass parameters or understand the generated 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?

Schema description coverage is only 29% (2 of 7 params described), yet the description adds no meaning for key parameters like stream_count, include_depth, include_tracking, or device_name. It fails to compensate for the low schema coverage.

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 clearly states it creates a DepthAI/OAK camera scaffold with specific components (OAK Device, OAK Select placeholders, stream maps, hardware-gated notes). This differentiates it from sibling tools like create_realsense_depth_bus or create_zed_depth_bus by identifying the exact hardware and scaffold elements.

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 versus alternatives, prerequisites, or exclusions are provided. The description only states what the tool creates, leaving the agent to infer when to choose this over other camera/device scaffolding tools.

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