switch_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 mentions 'Maps to Window.SwitchMode' but does not state side effects, prerequisites (e.g., Dorico must be running), or whether this is a state-changing operation.

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 short and front-loaded, with the purpose stated in the first sentence. However, the truncated phrase 'the ``kWriteMode``…' suggests incomplete content, slightly detracting from clarity.

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?

With a single parameter and no annotations, the description covers the core functionality but lacks information about return values, failure conditions, or prerequisites. The presence of an output schema reduces the need to explain return values, but behavioral context is still minimal.

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 schema provides only a string type with no description or enum. The description compensates fully by listing the allowed modes ('write', 'engrave', 'play', 'print', 'setup') and noting that kWriteMode forms are accepted. This is essential for correct invocation.

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 'Switch Dorico's window mode' with a specific verb and resource. It distinguishes itself from sibling tools like navigate, playback, and run_command by focusing on window mode switching.

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?

Usage is implied by the name and description, but no explicit guidance is given on when to use this tool versus alternatives. The listing of allowed modes provides some context for appropriate usage, but no 'when not to use' or alternative references are present.

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