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 mentions simulation and iOS-only, but fails to describe critical traits: whether this triggers system-level authentication dialogs, if it requires specific app permissions, what happens on match vs. mismatch (beyond the parameter), or any side effects like app state changes. For a security-related tool, this is a significant gap.

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 extremely concise—a single, front-loaded sentence with zero wasted words. It directly states the core functionality and constraint without any fluff, making it efficient for quick comprehension.

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 complexity of simulating a biometric feature with security implications, no annotations, and no output schema, the description is incomplete. It misses behavioral details, error conditions, return values, and integration context, leaving the agent under-informed for safe and effective use.

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 the single parameter 'match' fully documented in the schema. The description adds no additional parameter semantics beyond implying fingerprint simulation, which the schema already covers. Baseline 3 is appropriate as the schema does the heavy lifting, but no extra value is added.

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 action ('Simulate Touch ID fingerprint') and specifies the platform constraint ('iOS only'), which distinguishes it from generic biometric tools. However, it doesn't explicitly differentiate from sibling tools like 'unlock-device' or 'lock-device' that might involve device security, leaving some ambiguity about its unique role in the toolset.

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 guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., requiring an iOS device or simulator setup), typical use cases (e.g., testing authentication flows), or exclusions (e.g., not for Android). This leaves the agent to infer usage from the tool name alone.

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