Create depth from 2D

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

The description discloses creation of a new container, wiring, and a depth Null TOP, consistent with readOnlyHint=false. It adds performance context (30–60s compile) and dependencies, going beyond 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?

The description is a dense but well-organized paragraph that covers purpose, dependencies, constraints, performance, and returns without wasted words. It's slightly long but every sentence contributes.

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 description covers purpose, requirements, OS limits, output fields, and downstream usage, making it quite complete for a tool with no output schema. It omits error scenarios but provides sufficient operational context.

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 100%, so baseline is 3. The description adds context about source_top_path and output_resolution/model_variant in the return list but doesn't significantly enhance param understanding beyond the schema.

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 converts any 2D image/video TOP into a depth map TOP using Depth Anything v2, with a specific verb and resource. It also distinguishes from siblings by mentioning downstream tools (create_depth_displacement, etc.) that consume its output.

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 specifies prerequisites (installed TOX, NVIDIA GPU with CUDA/TensorRT), platform exclusion (macOS), and first-cook timing. It positions the tool as an alternative to hardware depth sensors ('no Kinect or RealSense required') and indicates typical integration by naming downstream consumer tools.

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