obsbot_tail2_info

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

With no annotations provided, the description carries the full burden, and it discharges the most important part by declaring 'Read-only', which tells the agent this is a safe non-mutating call. It also enumerates the returned data blocks in detail, though it says nothing about authentication, rate limits, or behavior when the camera is unreachable.

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?

One dense sentence that front-loads the verb and the payoff ('in one call') before enumerating contents; the trailing 'Read-only' is well placed. It is information-packed without padding, though the mid-sentence enumeration is a heavy run-on.

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?

No output schema exists, so the description properly takes on the job of describing return values, and it does so concretely for all three sub-blocks. The only real gap is the undocumented 'camera' argument, which leaves the agent unable to know how to target a device.

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 'camera' parameter has 0% schema description coverage, so the description is the only place meaning could be added, and it never mentions the parameter at all. With one undocumented parameter, the description fails to 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?

States a specific verb (Read) plus the resource (a Tail 2's identity and static configuration) and enumerates the three returned blocks (device_info, range, networkconfig), so the agent knows exactly what it gets. It does not, however, differentiate itself from nearby read siblings such as obsbot_tail2_status or obsbot_tail2_devices, which an agent must choose between.

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 phrase 'in one call' implies this is the consolidated read for static configuration, which hints at when to prefer it, but there is no explicit when/when-not statement and no named alternative. Usage is only implied, not stated.

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