nina_camera_capture

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explains blocking behavior (wait_for_result), side effects (saving, plate-solving, streaming), and data transfer concerns (omit_image for large payloads). It lacks authentication or error behavior details but is sufficient for a capture tool.

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 front-loads the core purpose in one sentence, then systematically lists parameter explanations. It is slightly verbose but well-organized. Each line conveys necessary information without excessive fluff.

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?

Given 17 complex parameters, no annotations, and no output schema, the description covers all relevant behavioral aspects—capture parameters, saving, processing, blocking, streaming, image size controls, and result handling. It equips an agent to use the tool correctly in diverse scenarios.

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%, yet the description thoroughly explains all 17 parameters with clear meaning and context (e.g., 'duration: exposure length in seconds', 'omit_image: keep this True unless you specifically want the pixel data'). This far exceeds the schema's bare type definitions.

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?

Description opens with 'Capture a single exposure,' a clear verb+resource statement that precisely defines the tool's core function. The tool name and this phrase unambiguously differentiate it from sibling tools like nina_camera_capture_statistics or nina_camera_abort_exposure.

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 explicit guidance on when to use this tool versus alternatives. The description lists parameters but does not explain scenarios for choosing capture over other camera tools, nor does it state prerequisites or contraindications.

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