get_camera_snapshot

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the current configuration state and the env vars required to make the call succeed. However, it says nothing about what the call returns (image bytes, base64, URL, or a content block) or how it fails, which is a meaningful gap for an image 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?

Two sentences with zero filler: the purpose and scope lead, and the blocking prerequisite follows immediately. Every clause earns its place.

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?

There is no output schema, so the description should carry more about the return value, and the lone parameter is undocumented. The config-state warning is genuinely useful, but a complete definition would also route the agent to list_local_cameras to discover a valid camera value.

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 'camera' parameter has 0% schema description coverage, so the description must compensate. It implies cameras are named/configured via DUET_CAMERAS but never states what values the parameter accepts (name vs. index vs. URL) or what happens when it is omitted.

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?

States a specific verb and resource ('Fetch a still image from a configured camera') plus the intended purpose ('to inspect the print or workspace'). It does not name or differentiate itself from the sibling list_local_cameras, which is the obvious adjacent tool, so it stops short of a 5.

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?

Gives a clear context of use (visual inspection of a print or workspace) and an actionable prerequisite: cameras are currently unconfigured and DUET_CAMERAS/DUET_CAMERA_URL must be set. It stops short of 5 because it never points to an alternative such as list_local_cameras for discovering valid camera names.

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