get_snapshot

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

Discloses main behavior (downloads to disk, returns file path) but lacks details on side effects (e.g., disk usage, overwrite behavior) or authentication requirements. With no annotations, description carries full burden; it is adequate but not thorough.

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 concise sentences: purpose, behavior/result, and usage context. Front-loaded and no unnecessary words.

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?

Covers core functionality, supported camera types, and prerequisite steps. Slightly incomplete as it doesn't describe return format details (e.g., file path format) but acceptable given no output schema.

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 already fully describes the parameter (cam_id as ID or URL). Description adds no additional param semantics; baseline 3 due to 100% schema coverage.

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 clearly states 'Fetch a live image from a camera' and specifies the output (file path). However, it does not differentiate from sibling 'get_snapshots' (plural), which may cause confusion.

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?

Provides context on which cameras it works with (upstream and locally-added) and recommends using list_cameras/search_cameras first. Does not explicitly mention when not to use or alternatives.

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