render_depth_map

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

Though no annotations are provided, the description explains the Z-pass usage, normalization, and color mapping (lighter closer). However, it does not state if the tool is destructive or returns a file, leaving some behavioral gaps.

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 concise, front-loaded with the main action, and includes a clear parameter list. Every sentence adds value without 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?

The description covers the core functionality and parameter, but lacks details on output format (e.g., whether the depth map is saved as an image) and integration with the compositor, which an agent might need.

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 description adds meaningful context to the 'max_depth' parameter by explaining it maps to black in scene units, which is beyond the schema's default and title. Since schema coverage is 0%, this aids agent understanding.

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 renders a normalized depth map from the active camera using the Z-pass, distinguishing it from siblings like 'render_from_camera' or 'render_all_cameras'.

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 guidance on when to use this tool versus alternatives like 'render_from_camera' or when not to use it. The description does not mention prerequisites or context.

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