services_camera_snapshot

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

No annotations are provided, so the description carries full burden. It discloses that the tool writes a file and specifies path constraints and allow-listing. However, it does not mention behavior on file overwrites, error handling, or entity validation, leaving some behavioral aspects ambiguous.

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 two sentences with no fluff. It front-loads the core action and adds necessary detail without excess.

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 simple two-parameter tool, the description covers the snapshot action and filename constraints. However, it omits explanation of the 'entity_id' parameter and does not describe the output schema or error scenarios, leaving some gaps.

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 coverage is 0%, but the description adds meaning to the 'filename' parameter by explaining its path convention and directory requirements. However, it provides no explanation for 'entity_id', leaving it undocumented. This partial coverage earns a baseline 3.

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 action: 'Take a still snapshot from a camera entity.' It uses a specific verb and resource, and distinguishes itself from siblings like 'services_camera_record' (recording video) and other camera-related tools.

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 when to use the tool (to capture a snapshot) and important preconditions: filename must be a path inside the HA config dir, directory must exist and be allow-listed. It does not explicitly state when not to use or mention alternatives, but given the tool's specificity, the guidance is clear.

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