Switch Mode

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

The description adds meaningful behavioral context beyond the annotations by explaining what LOCAL and CLOUD mean (AppleScript/macOS apps vs iCloud protocols). While it does not detail side effects or return values, the annotations (idempotentHint: true, destructiveHint: false) already provide a safety profile, and the description aligns with the readOnlyHint being false (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 a single, concise sentence that front-loads the verb and resource. It contains no wasted words and clearly communicates the tool's purpose in a compact format.

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 1-parameter tool with a well-documented enum, the description is largely complete. It explains the modes and the tool's function, though it does not explicitly describe the result of the switch or any side effects. Given the low complexity and rich schema, this is sufficient.

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 already provides 100% coverage for the 'mode' parameter with an enum and detailed property description. The tool description does not add meaningful information about the parameter beyond what the schema already states, so the baseline of 3 is appropriate.

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's function: switching between LOCAL and CLOUD modes. It uses a specific verb ('Switch') and resource ('mode'), and distinguishes this tool from siblings by describing the exact modes involved (AppleScript/macOS vs iCloud).

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 gives clear context that this tool is for toggling between two modes, with no ambiguity about when to use it. However, it does not explicitly mention alternatives or exclusions, though none are obvious given the sibling list. This is a clear context without exclusions.

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