Uninstall failover LaunchAgent

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

The description discloses key behavioral traits: it is destructive (moves plist to Trash), it does not remove persistent Clash profile changes, and it requires confirmation. This goes beyond the annotations (destructiveHint=true, idempotentHint=true) by specifying exactly what is affected and the confirmation requirement. No contradiction with annotations.

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 three concise sentences, each providing essential information: the core action, what is not removed, and the prerequisite. No wasted words, and the most important information is front-loaded.

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 description covers the core action, scope limitations, and prerequisites. The output schema is provided, so return values are handled separately. It is slightly incomplete in not addressing the config_path parameter or potential effects of not providing confirmation, but for an uninstall tool with a narrow purpose, it is largely 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 description adds crucial meaning for the confirmation parameter, specifying the exact required value 'UNINSTALL_LAUNCH_AGENT'. However, it does not explain the 'config_path' parameter at all, leaving its purpose ambiguous. Since schema coverage is 0%, the description only partially compensates for the lack of parameter documentation.

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 specific action: 'Stop the monitor and move its plist to Trash.' It identifies the resource (monitor/plist) and verb, and distinguishes itself from siblings like stop_monitor by clarifying it also removes the plist and mentions persistent Clash profile changes are not removed. The title 'Uninstall failover LaunchAgent' aligns with the description.

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 clear usage context: it requires mutation opt-in and a specific confirmation value ('confirmation=UNINSTALL_LAUNCH_AGENT'). It implies this is the tool for full uninstall rather than just stopping (stop_monitor). However, it does not explicitly name alternatives or exclusions, so it falls short of a 5.

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