camera_status

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

With no annotations provided, the description carries the full behavioral burden. It implies a read-only status read but says nothing about freshness (live query vs cached), permission requirements, or behavior for an unknown/nonexistent camera name.

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?

A single short sentence with no padding, and the payload contents are front-loaded. It is terse to the point of being fragmentary, but nothing is wasted.

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?

An output schema exists, so return structure need not be explained, and the description usefully hints at the payload contents. However, for a tool with no annotations and an undocumented parameter, it leaves open how the camera is selected and whether the status is live or cached.

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 0% for the single 'name' parameter, and the description only refers vaguely to 'one camera' without explaining that the camera is identified by the name argument or noting the eufy_cam1 default. It does not compensate for the coverage gap.

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 the resource ('one camera') and enumerates the payload ('ready state, tracks, and error counters'), which lets an agent distinguish this from snapshot_camera or list_cameras. It is a noun phrase rather than a verb+resource statement, so it is clear but slightly under-specified about the action being a retrieval.

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?

There is no guidance on when to reach for this tool versus siblings like list_cameras or snapshot_camera, and no conditions or exclusions are stated. The agent must infer usage from the payload description alone.

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