Mobile Next MCP

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

The annotations provide 'destructiveHint: true', which already indicates this is a destructive operation. The description adds minimal behavioral context beyond this - it confirms the destructive nature ('Uninstall') but doesn't elaborate on what 'uninstall' entails (permanent removal, requires permissions, potential side effects). No contradiction with annotations exists.

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 communicates the core purpose without any wasted words. It's appropriately sized for a straightforward destructive operation and gets directly to the point.

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 destructive tool with no output schema, the description is insufficient. It doesn't explain what happens after uninstallation (success/failure indicators, error conditions, or what the tool returns). Given the destructive nature and lack of output schema, more behavioral context about the operation's consequences would be needed for completeness.

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?

With 100% schema description coverage, both parameters are fully documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema descriptions. The baseline score of 3 reflects adequate coverage through the schema alone.

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 ('Uninstall') and target ('app from mobile device'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'mobile_terminate_app' or 'mobile_list_apps', which would require mentioning it's a permanent removal operation rather than just stopping an app.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing to identify the device first using 'mobile_list_available_devices'), when not to use it, or how it differs from related tools like 'mobile_terminate_app' (which stops but doesn't remove).

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