raw_device_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly warns that the tool 'may open a dialog or change project state' despite being described as static, and advises caution. This is valuable transparency, though the instruction to 'inspect the command name first' is vague and not actionable.

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 short and mostly front-loaded. The 'DeviceInfo:' prefix adds little, and the final clause is slightly cryptic, but the overall message is delivered in just two sentences without unnecessary 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 no-argument tool, the description covers purpose and potential side effects, but it omits what the returned technical information looks like and does not identify any sibling tools for comparison. Given the absence of an output schema and annotations, a bit more context about expected output or when to prefer this over raw_midi_device_info would improve completeness.

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 full schema coverage, so there is little for the description to add. The description reinforces that this is a 'no-argument' action, which is sufficient for a parameterless tool.

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 uses a specific verb and resource: 'Show technical information about audio devices.' It is clear enough to distinguish from raw_midi_device_info, though it does not explicitly exclude raw_input_device/raw_output_device or name sibling alternatives.

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 no guidance on when to use this tool versus alternatives. It notes the action is static and no-argument, but does not explain when a user should call raw_device_info instead of raw_midi_device_info or other device-related commands.

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