List Remote Devices

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

Annotations already provide readOnlyHint=true, and the description does not contradict this. It adds valuable operational context: remote devices are not usable until reserved, reservations may be limited or billed, and authentication is required. This goes beyond what the annotations convey.

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 front-loaded with the core purpose, then differentiates from the sibling tool, then explains constraints and prerequisites. Every sentence earns its place and there is no filler.

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 zero-parameter, read-only listing tool, the description is complete. It explains what the tool returns, how it differs from the local-device tool, when reservation is needed, billing implications, and the authentication prerequisite.

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?

The tool has zero parameters and the empty schema already fully documents this. The description adds no parameter details because none are needed, and it instead usefully describes what the returned catalog contains.

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 states a specific verb ('List') and resource ('catalog of device models ... remote cloud device fleet'), including the returned fields (make, platform, OS version). It also explicitly distinguishes this from mobile_list_available_devices, making sibling differentiation clear.

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 clearly explains when this tool is appropriate: when the user needs remote cloud devices, not locally connected devices. It names the alternative tool (mobile_list_available_devices), states the prerequisite (mobile_login_to_cloud_provider), and provides a retry strategy on authentication failure.

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