Set perform mode

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

The description discloses all key behaviors: it stores a flag on the TD root op, does not stop the timeline or kill A/V processing. It also explains the advisory guard. No annotations are contradicted; the readOnlyHint=false is consistent with writing a flag.

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?

Two sentences that are front-loaded with the action and purpose. The first sentence states the core function, the second explains scope and correct usage. No wasted words.

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 simple toggle with one parameter and no output schema, the description fully covers behavior, side effects, and usage pattern. It is complete and leaves no ambiguity.

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' already has a detailed schema description. The tool description adds context about flag storage and the built-in guard, providing extra meaning beyond the schema.

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 verb ('Toggle') and the resource ('perform mode'), and explains its purpose as an advisory flag for nonessential compute. It is distinct from sibling tools, which are all about creating or managing other elements.

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 explicitly says when to use: 'before going live' and after the show. It gives context like 'the one switch the artist flips before going live' but doesn't mention when not to use it or alternatives, though none are needed for a toggle.

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