Set perform mode

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

The description goes beyond annotations (readOnlyHint=false, destructiveHint=false) by detailing that it stores a flag on the TD root op, that the flag is advisory, and that it currently suppresses auto preview captures. No contradictions with annotations.

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 4 sentences that efficiently communicate purpose, usage, and behavior. The first sentence is front-loaded with the key action, making it easy for an agent to quickly grasp the tool's function.

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?

Given the tool's simplicity (one boolean parameter) and the presence of clear annotations, the description covers all essential aspects: when to use, behavioral effects, storage location, and what it does not do. It is fully adequate for correct invocation.

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 single parameter 'enabled' is thoroughly described in the input schema itself (100% coverage), so the description adds minimal new semantic value beyond what the schema already provides. The description reiterates key points but does not significantly extend meaning.

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 toggles perform mode, specifying it sets an advisory flag and suppresses auto preview captures. It distinguishes itself from other tools by framing it as 'the one switch the artist flips before going live,' which is unique among siblings.

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?

It explicitly states when to use (before a live show) and when not to (after show, to resume normal operation). It also clarifies what the tool does not affect (timeline, audio/video processing), providing clear context for appropriate use.

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