switch_profile

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

No annotations provided, so description must cover behavioral traits. Only states 'switch' without disclosing side effects (e.g., whether it affects ongoing streams, if profiles are loaded immediately). Does not describe error behavior or persistence.

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 is concise but lacks structure for parameters. Could include brief param explanations without adding length.

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?

No output schema and no annotations. Description does not specify return value, errors, or behavior when profile doesn't exist. Incomplete for a tool with 2 params and no structured metadata.

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% (no descriptions in schema properties). Description adds no meaning to parameters like 'dry_run'—does not explain its purpose (e.g., test without applying). Agent cannot infer how to use the dry_run parameter correctly.

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 the tool switches OBS profiles and clarifies what a profile is ('stream settings bundle'), distinguishing it from sibling tools like list_profiles (listing) or switch_scene_collection (scene collections).

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 guidance on when to use this tool vs alternatives (e.g., list_profiles to see available profiles) or prerequisites. Does not mention that profiles must exist beforehand.

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