obsbot_tail2_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 discloses the transport semantics ('one WebSocket push', i.e. a point-in-time snapshot) and a real capability limit (no live yaw/pitch, poses only via saved presets, so gimbal moves are open-loop). It stops short of stating permissions, error behavior, or refresh/caching semantics.

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 long comma-delimited field list is front-loaded after the verb and every item earns its place because there is no output schema to document the return shape. The trailing NOTE is justified as a caveat, though the sentence is dense.

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?

With no output schema and no annotations, the description steps in and documents the return contents field-by-field plus the key limitation. Only the camera parameter and any failure/timeout behavior remain uncovered.

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 single optional 'camera' parameter has 0% schema description coverage and is never mentioned in the description, so an agent gets no guidance on what value to supply or how it selects among multiple devices. The neighboring obsbot_tail2_devices/obsbot_tail2_scan tools imply multi-device setups where this matters.

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 ('a Tail 2's full live status block') and then enumerates the exact fields returned, so an agent knows precisely what this yields versus the single-purpose siblings like obsbot_tail2_gimbal_position or obsbot_tail2_preset_list.

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?

Usage is implied by the completeness of the status block, but the description never says when to prefer this over the sibling obsbot_tail2_info or the generic obsbot_status, nor when to fall back to obsbot_tail2_gimbal_position for live pose. No explicit when/when-not guidance is given.

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