osc_reset

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

With no annotations, the description carries the burden of explaining behavior. It does disclose the underlying action ('Send /eos/reset') and its effect, which adds useful transparency. However, it omits side effects, whether confirmation is needed, or any state-change warnings beyond 'clear OSC switches.'

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 one efficient sentence with the action front-loaded and the effect following. Every word adds value and there is no repetition or filler.

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?

Although the tool is simple, the description fails to explain the confirm parameter and gives no usage context relative to sibling OSC/EOS tools. There is no output schema and no annotations, so the agent is left with an incomplete picture for a mutating operation.

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%, so the description must explain the single 'confirm' boolean parameter, but it never mentions it. An agent cannot determine what confirm controls, its default behavior, or whether it affects the reset operation.

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 names a specific protocol command ('Send /eos/reset') and states the action's result ('clear OSC switches and refresh implicit output'), making the tool's function concrete. It does not explicitly contrast itself with generic siblings like eos_command, which prevents a 5.

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 is given on when to use this tool versus alternatives such as eos_command or macro_fire. The description implies when it might be appropriate but lacks explicit trigger conditions, exclusions, or comparisons.

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