camera_snapshot

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

Beyond readOnlyHint, the description discloses meaningful behavior: it does not move the printer, does not change lighting, and does not detect defects automatically, plus it requires LAN reachability. The return type (JPEG) is also named. It does not discuss latency, failure modes, or what happens on timeout, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core action and return type, followed by scope limits and the prerequisite. No redundant or filler wording.

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 single-purpose capture tool, the description covers action, return format, side-effect boundaries, and access requirement. The only gap is the undocumented timeout parameter, which matters for a network-dependent live read.

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?

There is one parameter (timeout_ms) with 0% schema description coverage, and the description never mentions it or explains what it controls or how it interacts with a live frame capture. The bounds (1000–30000) are visible in the schema, but the description does nothing to compensate for the missing semantics.

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 names a specific verb and resource ("Read one live A1 camera frame over LAN") and states the purpose (visual inspection of the bed and print). It does not explicitly contrast itself with siblings like printer_status, but the operation is distinct enough that confusion is unlikely.

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?

Usage context is clear — capturing a frame for visual inspection of the bed/print — and a prerequisite (LAN reachability from the MCP host) is stated. There is no explicit when-not-to-use guidance or pointer to a sibling tool, so it falls short of a 5.

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