obsbot_tail2_zone_tracking

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

With no annotations, the description carries the full burden and does so well: it discloses the transport (private UDP 9999, key 03), the critical fact that there is no ack and no REST-readable state, and that the effect must be observed indirectly in tracking behavior. That is exactly the kind of side-effect/no-confirmation detail an agent needs. It stops short of 5 because the verification cue ('effect shows in the tracking behavior') is vague about latency or how to confirm success.

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?

Front-loaded with the action and its UI equivalence, then the operational caveats. The capture date and TAIL2-PROTOCOL.md §10b citation are implementation provenance that does not help an agent select or invoke the tool, but they are brief.

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 no-annotation, no-output-schema, two-parameter mutation tool, the description covers the behavioral risks (no ack, no readable state) but leaves the `camera` parameter and the boolean's exact semantics undocumented. Adequate but with a clear gap on the input contract.

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 both parameters. The description's 'on or off' loosely explains `enabled`, but `camera` — arguably the more consequential parameter for a multi-device setup — is never mentioned or explained in either the schema or the description.

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+resource ('Toggle zone tracking') and anchors it to a known UI concept ('Center's Console page switch'), so the agent knows exactly what capability is being flipped. It does not, however, differentiate itself from plausible siblings like obsbot_tail2_ai_track or obsbot_tail2_track_custom, which also concern tracking behavior.

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 rather than stated: 'works with Center closed' tells the agent this path is usable when the app is not running, which is a real contextual cue. But there is no explicit when-to-use/when-not guidance and no naming of an alternative when the effect matters.

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