obsbot_focus_auto

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the immediate effect. It does not mention whether this overrides manual focus, whether it persists across sessions, or what observable side effects occur on the camera.

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 description is four words with zero filler, and the core action is immediately front-loaded. It is efficiently concise, though it verges on being too sparse to serve as a complete definition.

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 one-parameter tool with no annotations and no output schema, the description leaves important gaps: the meaning of the camera parameter and the behavioral implications of enabling continuous autofocus are unaddressed. It identifies the intent but is insufficient for reliable autonomous invocation.

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 only parameter 'camera' is an undocumented string with 0% schema description coverage, and the description never mentions it. An agent has no way to know what values are acceptable, what the parameter identifies, or whether it is safe to omit.

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?

The description states a clear action ('Enable continuous autofocus') on a specific resource, making the tool's intent immediately understandable. It distinguishes itself from obsbot_focus_manual by the word 'continuous', though it does not explicitly name or contrast itself with siblings.

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?

No guidance is provided about when to use this tool versus alternatives like obsbot_focus_manual or obsbot_focus_face. There is no context for when continuous autofocus is appropriate or why an agent would select this over other focus-related tools.

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