list_mobility_devices

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses pagination behavior (limit/offset, 200 max, all pages drained), the summary nature of results, and key routing semantics. It does not state auth/read-only assumptions, but for a list operation this is fairly complete.

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 compact and front-loaded: purpose, return content, pagination, then parameters. Every sentence adds information without redundant phrasing.

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 straightforward listing tool with an output schema, the description covers what is returned, how pagination is handled, and what each parameter means. No critical information needed to invoke it correctly is missing.

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%, and the description fully compensates by explaining both parameters: workspace_id is the workspace UUID from list_mobility_workspaces, and key_label is an optional configured API-key label used for key routing. This adds meaning beyond the bare schema types.

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 names a specific verb ('List') and resource ('UMR devices in a Mobility workspace'), and specifies the lightweight summary fields returned. The Mobility workspace scoping separates it from generic device-list siblings such as list_devices and list_site_devices.

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?

It clearly establishes the prerequisite and source for the required parameter ('workspace_id: the workspace UUID from list_mobility_workspaces'). It does not explicitly name alternatives or when-not-to-use it, but the workspace context and required parameter provide clear enough usage guidance.

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