MCP Appium Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by warning about 'requires user interaction', which is crucial for understanding that this is not a fully automated process. However, it lacks details on potential side effects, error handling, or what happens if tools are already installed.

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, efficient sentence that front-loads the core action ('Install Xcode command line tools') and adds essential behavioral context ('requires user interaction') without any wasted words. Every part of the sentence serves a clear purpose.

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?

Given the tool's complexity (installation with user interaction), no annotations, and no output schema, the description is reasonably complete. It covers the main action and a key behavioral constraint. However, it could be more comprehensive by addressing outcomes or error scenarios, though the lack of output schema limits this expectation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's purpose and behavioral aspects without unnecessary details.

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 specific action ('Install') and target resource ('Xcode command line tools'), distinguishing it from sibling tools like 'xcode_check_cli_installed' (which checks installation) and 'xcode_get_path' (which retrieves paths). It precisely communicates the tool's function without redundancy.

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 context for usage by stating 'requires user interaction', which implies this tool should be used when manual input or confirmation is needed during installation. However, it does not explicitly mention when to use alternatives like 'xcode_check_cli_installed' for verification or other installation-related tools.

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