obs-mcp-server

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

No annotations provided, so the description carries the full disclosure burden. It states the core mutation but omits critical behavioral details: whether changes persist across sessions, error conditions if the input_name doesn't exist, idempotency properties, or success indicators.

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?

Extremely concise at four words. While efficient and front-loaded with the action, this brevity is insufficient given the lack of annotations and sibling tool context. However, the sentence structure is direct and contains no redundancy.

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?

Adequate for a simple 2-parameter mutation with complete schema coverage, but leaves significant gaps regarding the relationship to `toggle_mute` and runtime behavior expectations. No output schema exists, but for a boolean setter this is acceptable.

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?

With 100% schema description coverage documenting both parameters clearly, the baseline is 3. The description adds minimal semantic value beyond the schema—essentially restating the `muted` parameter's boolean purpose and confirming the resource type as 'audio input' (already implied by the parameter name).

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 specific action (mute/unmute) on a specific resource (audio input). However, it fails to distinguish from the sibling tool `toggle_mute`, which performs a similar function using a different mechanism (toggling vs. explicit boolean setting).

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 guidance on when to use `set_mute` versus the sibling `toggle_mute`, or when to prefer this over `set_volume` (setting volume to 0). The schema parameter description references `list_audio_inputs` as a prerequisite, but the main description provides no usage context.

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