capture_image

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

With no annotations, the description carries full burden. It discloses that it captures an RGB image and returns metadata if output_path is not set. However, it does not mention any destructive or side effects, permissions, or constraints (e.g., camera must exist). Some useful behavior is stated, but lacking depth.

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 brief, with a clear first sentence explaining purpose, followed by a compact argument list. No redundant information. Every sentence 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 simple tool with two optional parameters and an output schema (though not shown), the description covers the essential behavior: capturing an image and saving to file or returning metadata. It does not explain metadata contents or output schema details, but the presence of an output schema partially mitigates that. Overall, fairly complete.

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%, so the description must compensate. It explains both parameters: prim_path as the camera's prim path and output_path as the file path to save the image, adding meaning beyond the schema. However, it omits details like file format or valid values. Overall, good but not exhaustive.

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 action ('capture'), resource ('RGB image from a camera sensor'), and the primary arguments. It distinguishes itself from sibling tools like 'create_camera' or 'get_scene_info' by focusing on image acquisition. The scope is well-defined.

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 when to use (when an image from a camera is needed) but does not explicitly state when not to use or provide comparisons to alternative tools like 'get_scene_info'. No context-sensitive guidance is given.

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