List the authenticated user's test suites. Pass suiteId to fetch a single suite together with its ordered items (tests + plans). Pass parentSuiteId to list only that suite's direct children; omit both to list every suite.
| Name | Required | Description | Default |
|---|---|---|---|
| suiteId | No | Fetch this single suite and include its items (tests + plans) | |
| parentSuiteId | No | List only suites whose parent is this id (use '' or omit for all) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose that items returned with a single suite are ordered (tests + plans) and that it operates on the authenticated user's suites. However, it does not describe the response shape, pagination behavior, or what happens with an invalid/nonexistent id, which leaves some ambiguity for a read tool with no annotation coverage.
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?
Three sentences, each earning its place. The first states the primary action and scope, the second explains the single-suite fetch mode, and the third clarifies the children vs all-suite distinction. Zero redundancy and front-loaded with the core purpose.
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 list/fetch tool with two optional parameters, zero required, no output schema, and full schema description coverage, this description is adequate. It explains all three usage modes and the ordering behavior of returned items. The main gap is lack of detail on return shape/pagination, but with no output schema and modest complexity, the description is reasonably complete.
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 both suiteId and parentSuiteId documented in the schema. The description reinforces these meanings by explaining the behavioral consequences of each parameter (fetch single vs list children), adding modest value over the schema. But it doesn't add format or syntax details beyond what the schema already provides, so the baseline 3 is appropriate.
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 it lists the authenticated user's test suites, with explicit distinctions for three modes: fetch single suite with ordered items, list direct children of a parent, or list all. This is specific and self-contained, and the verb (list/fetch) plus resource (test suites) is unambiguous. It effectively differentiates from related siblings like testrail_list_suites and test_suite_create.
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 explicit when-to-use guidance by explaining the effect of each parameter combination: pass suiteId to fetch a single suite with items, pass parentSuiteId to list direct children, omit both to list every suite. It also clarifies the children semantics (direct vs nested) which is critical for correct usage. This goes beyond what the schema alone conveys.
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.
