obsbot_tail2_live_status

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

With no annotations, the description carries the full burden and does well: it declares the operation is a read, notes the response is regenerated server-side per request (freshness semantics), and specifies the precise data categories returned. It omits auth/permission needs and any rate-limit or latency context, which keeps it short of a 5.

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 dense sentence front-loads the core action and then enumerates the payload; every clause adds discriminating detail (euler+joint angles, digital_enable, running shutter/ISO/aperture). The parentheticals approach over-packing but do not waste 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?

For a read-only GET with no output schema, the description adequately compensates by enumerating the returned fields (pose, zoom internals, exposure truth, temperatures, boot stage, accessory state). The only real gap is the undocumented camera parameter, which an agent needs in order to call the tool.

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?

There is one parameter (camera) with 0% schema description coverage, and the description never mentions it — no format, default, or meaning. The baseline of 3+ for schema-rich tools does not apply here since the schema documents nothing, so the description should have compensated but does not.

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 (Read) and resource (FRESH runtime snapshot from GET /camera/test/status) and enumerates what the snapshot contains. It further distinguishes itself from the WS push (no pose) and from the REST tree, so an agent can differentiate it from siblings like obsbot_tail2_status.

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?

Implicitly conveys when to use it — when you need a fresh per-request snapshot of things the REST tree or WS push hide (gimbal pose, zoom internals, running exposure). However, it never names sibling alternatives (obsbot_status, obsbot_tail2_status, obsbot_tail2_info) or states exclusions, so routing is left to inference.

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