list_utsLists usability tests across every workspace you can access — the usual starting point for finding a UT. Optional status filter (PREPARING / IN_PROGRESS / COMPLETED / ARCHIVED).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| status | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, so the safety profile is covered. The description adds the cross-workspace scope ('every workspace you can access') and the optional status filter, but does not disclose pagination behavior or return format. With annotations, this is adequate but not rich.
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 only two sentences, front-loads the primary purpose, and includes only essential details. No filler or repetition of schema fields.
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 simple list tool with no output schema, the description adequately conveys the core behavior and key filter. It omits the limit parameter's behavior and any pagination details, but these are minor given the tool's low complexity.
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 0%, so the description must compensate. It explicitly lists the status filter values and optionality, but does not explain the limit parameter. The description partially covers the parameters, leaving the limit's effect on results unspecified.
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 tool lists usability tests across all accessible workspaces, using a specific verb ('Lists') and resource ('usability tests'). It distinguishes from sibling tools like get_ut (single UT) and create_ut by indicating it is the 'usual starting point for finding a UT'.
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 clear usage context ('usual starting point for finding a UT') but does not explicitly mention when not to use it or name alternatives. Context signals show siblings like get_ut, but no explicit comparison is made.
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.
Every tool targets a distinct resource and action. Even get_ut, which returns comprehensive data, doesn't replace the specialized get_session, get_transcript, or get_quantitative_report for detailed views. No two tools have overlapping purposes.
All names follow a verb_noun pattern with underscores (e.g., add_task, get_ut, list_workspaces). The main inconsistency is using 'create' for UTs (create_ut) but 'add' for child entities (add_use_case, add_task), and having a separate update_scenario instead of folding it into update_ut, but the convention is still predictable.
With 18 tools, the set is slightly above the typical 3-15 well-scoped range, but the domain of usability testing requires distinct operations for drafting (use cases, tasks, scenario), reading results (reports, sessions, transcripts), and comparison. Each tool has a clear role, so the count feels reasonable rather than excessive.
The tool surface covers the core lifecycle: create, read, update, and delete for tasks/use cases, plus comprehensive retrieval of results and notes. Minor gaps include no delete_ut (UTs cannot be removed) and no explicit status change or cloning mechanism, but these are likely intentional app-side actions, so the surface is not severely incomplete.