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 context. It mentions 'send text input' which implies a write operation, but doesn't disclose whether this requires specific element states (focusable, visible), what happens if the element doesn't exist, whether it clears existing text first, or any error conditions. For a mutation tool with zero annotation coverage, this is inadequate.

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 with zero wasted words. It's appropriately sized for a tool with three parameters and gets straight to the point without unnecessary elaboration.

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 UI automation tool that performs text input (a mutation operation), the description is insufficient. With no annotations, no output schema, and minimal behavioral context, it doesn't provide enough information for safe and effective use. The agent won't know what happens on success/failure, what permissions are needed, or how this differs from similar sibling tools.

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%, so all parameters are documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema (selector types, text content, strategy options). It doesn't explain relationships between parameters or provide examples of valid selector formats.

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 input') and target ('to a UI element'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'send-keys-by-ios-class-chain' or 'send-keys-to-device', which appear to be similar text-input tools with different targeting methods.

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 about when to use this tool versus alternatives like 'send-keys-by-ios-class-chain' or 'send-keys-to-device'. The description doesn't mention prerequisites (e.g., whether an element must be focused or visible) or context about when text input is appropriate versus other interaction methods.

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