Start failover LaunchAgent

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

Annotations already indicate readOnly=false, idempotent=true, destructive=false. The description adds the confirmation requirement and clarifies that it restarts if already running, which aligns with the idempotent hint and adds context beyond annotations. No contradictions.

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 focused sentence with the action front-loaded. It contains no redundant phrases and includes the key requirement without wasting 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?

Despite having an output schema and simple purpose, the description fails to document config_path and leaves the 'mutation opt-in' mechanism unexplained. It also does not indicate when to use the tool versus related operations. The confirmation requirement is present, but the overall guidance is incomplete for a tool with zero schema descriptions.

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?

Schema coverage is 0%, so the description must explain parameters. It mentions the confirmation constant ('confirmation=START_LAUNCH_AGENT') but gives no explanation for config_path, which is left completely opaque. The agent knows confirmation's expected value but not what config_path does or when to set it.

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 uses a specific verb ('Start or restart') and identifies the resource ('installed monitor'), clearly distinguishing it from siblings like stop_monitor or install_failover. The title reinforces the target as the failover LaunchAgent.

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 provides a prerequisite (mutation opt-in and confirmation constant) but offers no explicit guidance on when to choose this tool over alternatives like install_failover or stop_monitor. The usage is implied by the name and title, but there are no exclusionary instructions or alternative references.

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