toggle_proxy_mode

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the change is global but omits whether the setting persists across sessions, whether it affects export/render output or only playback, and what happens when no proxies exist — all critical for a global state mutation.

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?

One short, front-loaded sentence with no waste. Minor deduction because 'toggle' sits slightly awkwardly against a boolean 'enable' parameter that explicitly sets state rather than flipping it.

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?

The tool is simple (one documented boolean param, no output schema), and the description conveys the core action and its global scope. It is still thin for an unannotated global mutation tool — the effects on playback vs. export and the persistence of the setting are unstated.

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?

With 100% schema description coverage, the single 'enable' boolean is fully documented in the schema ('True to enable proxies, false to use full-res'). The description adds only scope context ('globally') and no additional parameter semantics, 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?

States a specific verb+resource ('Toggle between proxy and full-resolution media') with a scope qualifier ('globally'), so an agent can identify the operation precisely. It does not explicitly distinguish itself from the sibling tools create_proxy/attach_proxy, which also deal with proxies, so the agent must infer the difference from the word 'globally'.

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 word 'globally' implies this is an application/project-wide switch as opposed to per-clip proxy creation, which is a useful implicit usage cue. However, there is no explicit statement of when to use this versus create_proxy/attach_proxy, and no preconditions (e.g. proxies must already be generated).

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