Create DepthAI OAK pipeline

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

Annotations already indicate the tool is mutating (readOnlyHint=false) and not destructive. The description adds context about scaffold components and 'hardware-gated setup notes,' but does not disclose potential side effects like overwriting existing nodes or idempotency. It neither contradicts annotations nor adds deep behavioral detail.

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?

The description is one concise, front-loaded sentence that efficiently lists the scaffold's key components without wasted words. Every phrase adds value.

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 tool with 7 parameters and no output schema, the description is minimal but gives an adequate high-level idea. However, it lacks details on prerequisites, concrete usage scenarios, or how hardware-gating works, making it incomplete for confident execution without further investigation.

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%, and the tool description does not explain any parameter meanings beyond the schema's sparse descriptions. The description mentions components like 'stream maps' but does not map them to parameters such as stream_count, include_depth, or include_tracking, leaving the agent to guess.

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 the tool creates a 'DepthAI/OAK camera scaffold' with specific components (OAK Device, TOP/CHOP placeholders, stream maps, setup notes), which is a specific verb+resource and distinguishes it from other create_* pipeline tools.

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 implies usage for DepthAI/OAK camera setups but does not explicitly state when to use it versus alternatives like create_voice_prompt_pipeline or create_depth_displacement. No exclusions or alternative mentions are provided.

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