obsbot_tail2_scan

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 richly: it discloses the mDNS listen window (~5s), the fallback HTTP subnet sweep and its cost (~20s on a full /24), and the crucial side effect that cameras 'stay registered afterwards'. This is the kind of persistence/timing/auth-relevant context an agent needs before invoking a network-scanning tool.

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 resource, then layered with timing and fallback detail; every sentence adds operational value. The parenthetical about OBSBOT Center is slightly decorative but supports trust in the discovery mechanism.

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?

With no annotations and no output schema, the description still states the return value ('Returns the cameras found'), the registration side effect, and the discovery strategy. Nothing an agent needs in order to call this correctly is missing.

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 tool takes no parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly does not invent options.

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?

Specific verb+resource: 'Discover OBSBOT Tail 2 cameras on the network and register them' tells the agent exactly what happens. Scope is further narrowed by 'onboard a Tail 2 whose IP you don't know', which implicitly separates it from the listing siblings (e.g. obsbot_tail2_devices), though no sibling is named explicitly.

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?

Clear usage context: 'Run this once to onboard a Tail 2 whose IP you don't know' states when the tool is appropriate. It does not name a specific alternative for the already-known-IP or already-registered case, so no explicit when-not guidance is given.

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