System Set Appearance Mode

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

The description adds no behavioral detail beyond what annotations already state. It does not disclose whether the change applies immediately, what side effects occur, or what permissions are required. Annotations include destructiveHint=false and idempotentHint=false, but the description contributes nothing additional.

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, but it is under-specified rather than genuinely concise. The single sentence restates the tool name and platform, providing almost no useful information while still occupying the available description space.

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?

Even though the tool has only one parameter and an output schema, the description is far too thin to support correct selection or invocation. It omits mode value semantics, behavioral effects, and any relationship to the many sibling system configuration tools.

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 only parameter, 'mode', has 0% schema description coverage and the description does not mention it at all. An agent cannot determine valid values (e.g., light/dark) or the expected format, so invocation would be speculative.

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 only restates the tool name in quotes and notes it is 'exposed through Apple-Tools-MCP'; it does not state what setting the appearance mode actually does. The name implies a setter operation, but the description itself provides no verb+resource explanation or differentiation from sibling tools.

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?

There is no guidance on when to use this tool versus related siblings like system_get_appearance_settings or apple_update_system_setting. No context, preconditions, or exclusions are provided, leaving the agent to guess the appropriate calling scenario.

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