emulate_list_devices

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

With no annotations, the description alone must convey behavior. 'List all available' explicitly indicates a non-destructive, read-only operation that returns a complete set of presets. No side effects, prerequisites, or other behavior need disclosure for a simple list tool.

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 a single, front-loaded sentence that states exactly what the tool does with no filler or redundant words. Every word earns its place.

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?

Given the tool's simplicity (0 parameters, no output schema) and its role among emulation siblings, the description is fully complete. It answers what the tool lists, for what purpose, and no further detail about return format or side effects is necessary.

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 schema description coverage is 100% (vacuously). Per rubric, baseline for 0 params is 4, and the description does not need to explain parameter semantics. It adds no extra param info, but none is required.

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 'List all available device presets for emulation' uses a specific verb ('List') and a clear resource ('available device presets for emulation'), making it distinct from sibling tools like emulate_device which actually applies a preset, or emulate_custom_device which defines custom ones.

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 implies a listing/read-only context for selecting presets when using emulation tools, and there are no exclusions or alternatives mentioned. While it does not explicitly say 'use before emulate_device', the context is clear and no closer sibling exists for this purpose.

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