camera_status

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

With no annotations, the description carries the full behavioral burden. It discloses key runtime behaviors: `position` is null without a live session, `startup_error` explains startup failures, and `stream_url` exposes the live video feed. It does not discuss side effects, but 'Report' implies a read-only operation and the disclosed field states are the most decision-relevant behaviors.

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 sentences, each earning its place: the first states the tool's purpose, the second gives critical ordering guidance, and the third explains the stream URL. It is front-loaded and free of filler.

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 zero-parameter status tool with an output schema, the description covers the essential context: what it reports, when to call it, why it matters, and how to interpret key fields. Nothing critical is missing for correct invocation.

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 tool has zero parameters, so the input schema provides no parameter semantics to clarify. The description instead adds meaning to the output fields, which is the relevant semantic content for a status tool.

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 opens with a specific verb and resource: 'Report the camera's orientation, travel limits and session state.' This clearly distinguishes it from the pan/tilt and snapshot siblings as a status/read tool, not a control or capture tool.

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 explicitly tells the agent to call this first and explains why: `position` is null until a live session exists, which indicates other tools will fail. This is direct when-to-use guidance with a concrete alternative-aware rationale.

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