Enable or disable loop mode on a TriCaster DDR media player by specifying DDR 1 or 2 and a boolean enabled state.
Enable or disable loop mode on a DDR (media player).
| Name | Required | Description | Default |
|---|---|---|---|
| ddr | Yes | DDR number (1 or 2) | |
| enabled | Yes | True to enable loop, False to disable |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not say whether enabling loop restarts playback, whether the setting persists across clips or reboots, whether it requires the DDR to be playing, or what errors occur if the DDR is idle — all material for a mutation tool.
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?
A single tight sentence with no filler, front-loading the action and target. Nothing could be trimmed without losing meaning.
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 two-parameter boolean toggle with full schema coverage and no output schema, the definition is nearly sufficient — the required inputs are unambiguous. It falls short only on behavioral context (persistence, interaction with playback state, permissions) that the absence of annotations leaves uncovered.
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 100%, so both parameters are already documented in structured form (DDR number 1 or 2, boolean enable/disable). The description adds only the gloss that 'DDR' means media player, so the baseline 3 applies.
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?
Clear specific verb (enable/disable) plus the resource and its controlling field (loop mode on a DDR media player). It does not, however, differentiate itself from the sibling ddr_set_autoplay, which is a closely related per-DDR playback toggle an agent could easily confuse it with.
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 states what the tool does but gives no guidance on when to use it versus ddr_set_autoplay, ddr_play, or ddr_stop, and no prerequisites or state conditions. The agent is left to infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.