obsbot_tail2_only_me

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the dual read/write invocation model, which is non-obvious and valuable. It does not describe side effects (e.g., whether enabling OnlyMe disables other tracking modes), permission/auth needs, or failure behavior.

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 well-formed sentence that front-loads the read/set modes and then explains the feature semantics. No filler, every clause earns its place.

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 simple two-parameter device switch with no annotations or output schema, the description covers invocation modes and feature meaning adequately. The unnamed 'camera' parameter and undisclosed side effects are the only remaining gaps.

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%, so the description must compensate. It conveys that 'enabled' drives the set operation but says nothing about the 'camera' parameter (target device selection) and gives no type/format details. Partial compensation only.

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?

Names a specific verb pair (read/set) and a specific resource (the OnlyMe human-tracking switch), and elaborates what the switch does functionally ('track only the nearest/locked person rather than reframing for everyone'). It does not explicitly distinguish itself from tracking siblings like obsbot_tail2_ai_track or obsbot_tail2_track_target, so it stops short of a 5.

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?

Gives concrete operational guidance: a bare call reads the current state, while passing 'enabled' sets it. This tells the agent how to invoke either mode. It does not, however, say when to prefer this over the broader AI-tracking tools, so the routing guidance is incomplete.

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