streamfog_clear_effects

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

The description discloses that the tool dispatches the 'ClearEffects' action to Streamer.bot and returns the camera to baseline. It also includes the return format. Annotations only provide readOnlyHint=false, and the description adds meaningful behavioral context beyond that.

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 concise with three sentences covering purpose, action dispatch, return format, and an example. Every sentence is valuable and 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 tool with an output schema, the description fully covers behavior, action, return format, and provides an example. No additional context is needed.

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 no parameters, so the description does not need to add parameter meaning. The schema coverage is 100% (empty), and the baseline for zero parameters is 4.

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's function: 'Strip all active AR assets, face filters, and canvas overlays' and 'Returns the camera feed to a clean, unfiltered video baseline.' This is specific and distinct from sibling tools like streamfog_set_lens or streamfog_toggle_avatar.

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?

The description implies usage when effects need to be cleared, but it does not provide explicit guidance on when to use versus alternatives, nor does it mention prerequisites or exclusion conditions.

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