obs_health

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 describes the returned data and the read-only nature implicitly ('health snapshot'). It could add caveats like 'requires OBS running' or 'non-destructive', but the term 'snapshot' conveys safety and comprehensiveness.

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 two sentences: the first statefully lists all returned data, the second gives usage guidance. No filler or redundancy, and the most important information is front-loaded.

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 zero-parameter diagnostic tool with no output schema, the description enumerates all expected data items and explains when to use it. It fully covers what the agent needs to know to select and invoke the tool correctly.

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 has zero parameters, so there is nothing to explain. The description correctly focuses on the output rather than inputs, which is appropriate and provides a good default for no-parameter tools.

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 clearly states it's a 'Full health snapshot' with a specific verb ('snapshot') and resource (OBS health). It enumerates exact data fields (OBS version, active scene, stream/record state, live stats). It also distinguishes itself from siblings by positioning as the first diagnostic step.

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?

It explicitly says 'Use this first to diagnose anything, and to check whether the machine is keeping up,' providing clear when-to-use guidance. It doesn't name specific alternatives or exclusions, but the 'first' directive implies a diagnostic workflow where more specific tools follow.

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