obsbot_tail2_antiflicker

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

No annotations are provided, so the description carries the full burden. It does add a genuinely useful behavioral trait – 'Readback-verified write' tells the agent the write is confirmed by a read-back – but it omits permission requirements, failure behavior, and what a read returns.

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?

A single dense sentence with the action front-loaded and no filler; the enum caveat is parenthetical and does not derail the reading. Slightly terse for the load it must carry, but structurally sound.

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 2-param tool with no output schema and no annotations, the description covers the core action and the read-back verification but leaves gaps: it does not explain what a read returns, what the 'camera' parameter designates, or how failures surface.

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 2 parameters, so the description must compensate. It reinforces the enum values and adds the caveat that 60hz was measured on this unit, but the 'camera' parameter is completely undocumented and the read/write semantics of omitting 'mode' are left to inference.

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 and resource: read or set the anti-flicker mode, and enumerates the valid values (off, 50hz, 60hz). It is clear what the tool touches; the only reason it is not a 5 is that it gives no sibling differentiation, though no sibling covers anti-flicker.

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 'Read or set' implies the usage contract (omit mode to read, supply mode to write), and the required-parameter count of 0 supports that reading, but the description never states the when-to-use condition or any prerequisites explicitly.

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