MCP Appium Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose what happens on failure (e.g., timeout behavior), whether the tool waits for element visibility, if it clears existing text first, or any side effects. 'Send text' implies a write operation, but safety implications are unspecified.

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?

Extremely concise single sentence with zero wasted words. Every component ('Send text', 'to an element', 'using iOS class chain', 'iOS only') serves a distinct purpose. The structure is front-loaded with the core action immediately clear.

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?

For a 3-parameter tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens on success/failure, return values, error conditions, or interaction patterns. Given the complexity of mobile automation and multiple sibling alternatives, more context about when and how to use this specific tool is needed.

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%, providing complete parameter documentation. The description adds no additional parameter semantics beyond what's in the schema - it mentions 'iOS class chain' and 'text' but provides no extra context about format, constraints, or usage patterns. Baseline 3 is appropriate when schema does all the work.

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 ('Send text') and target ('to an element using iOS class chain'), with platform specificity ('iOS only'). It distinguishes from generic 'send-keys' by specifying the iOS class chain method, but doesn't explicitly differentiate from sibling 'send-keys-by-ios-predicate' which serves a similar purpose with a different locator strategy.

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 minimal guidance - it mentions 'iOS only' which helps exclude non-iOS contexts, but offers no explicit when-to-use advice versus alternatives like 'send-keys-by-ios-predicate' or regular 'send-keys'. No prerequisites, error conditions, or performance considerations are mentioned.

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