Run a low-level iOS device-management command. Pass the subcommand and optional arguments. No automation session required. Example: subcommand="syslog", args=["--parse"]
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | Additional arguments for the subcommand | |
| udid | Yes | iOS device UDID | |
| subcommand | Yes | Device-management subcommand (e.g. "info", "syslog", "diskspace", "ip", "devicename") |
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 'low-level' and 'no automation session required' but doesn't disclose potential risks (this is a low-level command that could mutate device state), authorization requirements, expected output format, or whether certain subcommands are destructive. For an unannotated low-level shell 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?
Two sentences plus an example — efficient and front-loaded with the core purpose. The example is valuable and placed at the end. No wasted words, though the example could arguably be more comprehensive.
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?
This is a low-level passthrough tool with no output schema and no enumerated subcommands, meaning the description and schema must compensate. The description lists example subcommands but doesn't enumerate what each produces, note any failure modes, or explain the args format beyond the example. For a tool that exposes arbitrary device-management subcommands, this is under-specified.
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% (all three parameters documented in the schema). The description adds a concrete example showing how subcommand and args combine ('subcommand="syslog", args=["--parse"]') and hints at available subcommand values via the schema ('info', 'syslog', 'diskspace', 'ip', 'devicename'). The example adds modest value beyond the schema, earning baseline 3.
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 'Run a low-level iOS device-management command' with a specific verb and resource (iOS low-level command execution). It provides a concrete example (syslog --parse) that demonstrates real usage. However, it doesn't explicitly distinguish itself from the closely-related sibling tools like device_shell or other iOS shell variants, and the generic 'low-level' phrasing could apply to several tools.
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 states 'No automation session required,' which is a useful context signal that differentiates this from session-based tools. However, it doesn't clearly state when to use this tool vs alternatives like device_shell, ios_diagnostics, or other device-management tools. There's no exclusion guidance or mention of alternative tools for similar tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set contains near-identical duplicate families: web_* and playwright_* expose ~15 pairs of the same desktop-grid-browser operations (web_get_text/playwright_get_text, web_reload/playwright_reload), and screenshot/log/network/mock capabilities each have 5-8 entry points (device_screenshot vs android_mjpeg_screenshot vs ios_screenshot vs ios_fast_screenshot vs web_screenshot vs webpage_screenshot vs session_screenshot). Many individual descriptions carefully draw boundaries (devtools vs traffic, HID vs session), but an agent cannot reliably distinguish web_* from playwright_*, and ios_screenshot/ios_fast_screenshot/ios_mjpeg_screenshot blur together.
The prefix scheme is broken: Android functionality is split arbitrarily between android_* and device_* (device_screenshot vs android_mjpeg_screenshot), the desktop browser gets two parallel prefixes (web_* and playwright_*), and verbs vary across equivalents (device_navigate_url vs web_navigate vs ios_safari_navigate). session_* uses bare verbs (session_url, session_back), and the same concept gets different names (ios_clipboard_get_hid vs ios_get_pasteboard; device_screen vs ios_orientation).
333 tools is an extreme count by any measure — far beyond the 50+ threshold — and much of the bulk is duplicative (the web_*/playwright_* pairs alone double ~15 slots) or out-of-scope for a device-control server (TestRail, Jira, AzDO, agent memory, secret variables, feedback). Even granting that remote device control + test automation is a broad domain, this surface will devastate agent context budgets and is impossible to navigate coherently.
The core device-control and test-automation domain is remarkably thorough: Android and iOS each have full interaction, app-lifecycle, file, network/proxy, performance, crash, accessibility, recording, and replay coverage, with CRUD lifecycles for flows, suites, app uploads, TestRail cases, and visual-review baselines. Minor gaps exist at the margins — Jira/AzDO lack update/transition/comment operations, and iOS cannot open/close tabs — but the central workflows have no dead ends.
