raw_midi_device_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly warns that the tool 'may open a dialog or change project state' and advises to 'inspect the command name first,' acknowledging potential side effects. However, the warning is vague about what exactly happens (dialog vs. state change) and does not explain the nature of the information shown or any side effects in detail.

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: two sentences plus a brief warning. It front-loads the purpose (show info) and then provides behavioral cautions. There is no filler or repetitive content beyond the 'MidiDeviceInfo:' prefix, which is slightly redundant but not harmful. The structure is efficient for an agent reading it quickly.

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 (no parameters, no output schema), the description covers the essentials: what it does and a warning about potential side effects. However, it does not specify what information is returned or how the agent might verify the output, and the 'inspect the command name first' advice is cryptic. For a tool that may change state, more clarity on what triggers side effects 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 schema has zero parameters and 100% coverage (vacuously). The description adds 'Static no-argument Audacity action,' which reinforces the empty schema but does not provide any additional parameter semantics beyond what is already known. Per the baseline for high coverage, a 3 is appropriate.

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 the purpose clearly: 'Show information about MIDI devices' — a specific verb and resource. It is distinguishable from siblings like raw_device_info (general device info) and raw_input_device/raw_output_device, though it does not explicitly name them. The phrase 'Static no-argument Audacity action' adds clarity about how it is invoked.

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?

No guidance on when to use this tool versus alternatives. It only notes that it is a static no-argument action, which says nothing about the appropriate context or how it differs from related device-information tools. There is no mention of prerequisites or exclusions, leaving the agent to infer when this is the right choice.

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