MCP Appium Server

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

No annotations are provided, so the description carries the full burden. It mentions 'perform a specific action' but doesn't disclose behavioral traits such as error handling, side effects (e.g., UI changes), performance implications, or response format. For a tool with multiple actions and parameters, this lack of detail is a significant gap, though it doesn't contradict any 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 a single, efficient sentence that states the core function without waste. It is appropriately sized and front-loaded, but could benefit from more detail given the tool's complexity. No redundant information is present, making it concise yet under-specified.

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 (5 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values, error cases, and practical usage examples. With rich input schema but no behavioral context, the description doesn't provide enough information for effective tool invocation in a UI automation context.

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 description coverage is 100%, with clear descriptions for all parameters, including enums for 'action' and 'locatorType'. The description adds no additional meaning beyond the schema, as it doesn't explain parameter interactions or provide examples. With high schema coverage, the baseline is 3, but the description fails to compensate with any extra insights.

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 states the tool performs actions on elements using locator strategies, which is a vague purpose. It mentions 'specific action' without detailing what actions are available, and while it distinguishes from some siblings like 'clear-element' or 'tap-element' by being more generic, it doesn't clearly differentiate from others like 'inspect-and-act' or 'perform-touch-id'. The verb 'perform' is generic, and 'element' is broad without specifying UI context.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for element interactions but doesn't specify scenarios, prerequisites, or exclusions. With many sibling tools for similar actions (e.g., 'tap-element', 'send-keys', 'swipe'), the lack of differentiation leaves the agent without clear decision criteria.

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