grab

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: saves to PNG, handles trigger modes, timeout behavior, and returns size/pixel format/path. It does not mention errors or permissions, but for a simple capture tool this is sufficient.

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 extremely concise with two paragraphs. The first sentence states the core purpose, the second adds trigger mode context. Every sentence earns its place, and it is front-loaded.

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 the presence of an output schema (so return values need not be described), the description covers the essential behavior (capture, save, trigger mode, parameter semantics). Sibling tools are unrelated, so no confusion. The description is complete for this tool.

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 single parameter save_path has 0% schema description coverage, but the description fully compensates: it explains that if omitted, the file saves to a temp directory and the path is returned. This adds significant meaning 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 verb 'acquire' and resource '1 frame', and specifies the actions: save as PNG, return size/pixel format/path. It is distinct from sibling tools (connect, add_producer, etc.) that manage camera connections and features.

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 explains when to use based on TriggerMode: 'On' waits for trigger, 'Off' for free-run. It suggests calling set_feature('TriggerMode', 'Off') for free-run capture. While it doesn't explicitly list alternatives or exclusions, the context is clear enough.

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