obs-mcp-server

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

With no annotations provided, description must carry full behavioral burden. 'Get' implies read-only operation, establishing safety profile. However, lacks disclosure of return format/types (booleans vs strings), potential error states, or caching behavior. Meets minimum expectations but provides no additional behavioral context beyond the implied read-only nature.

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?

Single sentence, nine words. Action-verb front-loaded with colon-separated enumeration of status components. No redundancy, tautology, or filler. Every word contributes essential information about tool capability.

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 parameterless status retrieval tool without output schema, description adequately covers functional scope by enumerating the three specific status components returned. Could be improved by hinting at return structure or value types (e.g., boolean for states), but sufficient given low complexity.

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?

Input schema contains zero parameters. Per scoring guidelines, zero-parameter tools receive baseline score of 4. Description appropriately makes no parameter claims, requiring no semantic clarification beyond what the empty schema already conveys.

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?

Excellent specificity: verb 'Get' + resource 'OBS status' + explicit scope enumeration ('active scene, streaming state, recording state'). Effectively distinguishes from action-oriented siblings like start_streaming/stop_recording and from list-oriented siblings like list_scenes by emphasizing current/active state retrieval.

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 explicit when-to-use guidance or alternative recommendations provided. However, the enumeration of returned status fields implicitly signals this is for monitoring current state vs. the mutation tools (set_scene, start_streaming). Adequate but lacks explicit guidance.

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