camera_snapshot

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

With no annotations to rely on, the description thoroughly discloses behavioral traits: the protocol differences (TCP vs RTSP), the default timeout of 8000ms, the cold start delay, and the deprecated/ignored experimental flag. This gives agents a complete understanding of what to expect.

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: two sentences that front-load the purpose and key behaviors. Every word adds value, with no filler or redundant information.

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 tool's complexity (multiple protocols, optional parameters) and rich schema descriptions, the description covers all essential aspects: what it does, protocol selection, output format, and key parameter behaviors like timeout. No output schema exists, but the return format is specified, so agents have sufficient 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 the schema already documents each parameter. The description adds some context (e.g., protocol routing, timeout default) but does not significantly enhance meaning beyond the schema definitions. Baseline 3 is appropriate.

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 captures a single JPEG frame from the printer's chamber camera, specifies the return format (base64), and differentiates between protocols for different printer models. This provides a specific verb and resource, making the tool's purpose unmistakable.

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 provides clear context on when to use the tool (to capture camera frames) and distinguishes protocol usage by model. It does not explicitly state when not to use it or provide alternatives, but among sibling tools there is no direct competitor, so the guidance is sufficient.

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