List Pd Audio Devices

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

The description discloses that the query is 'best-effort' and depends on a 'configured Pd binary', which hints at potential failure or configuration requirements. However, it does not explain what happens on failure, what exactly is returned, or any side effects. With no annotations, some transparency is present but limited.

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, concise sentence that front-loads the core action ('Best-effort query'). No unnecessary words or repetition, making it highly efficient.

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?

The tool is simple with no parameters and no output schema. The description adequately conveys the purpose and the best-effort nature, though it could mention the expected return format or error behavior. Given the low complexity, the description is nearly complete.

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 schema is empty with 100% description coverage. Since there are no parameters to document, the description need not explain any parameter semantics, and the baseline of 4 applies.

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 clearly states the tool performs a query of Pd audio devices using the configured Pd binary. The verb 'query' and the resource 'Pd audio devices' make the purpose unmistakable, and it is distinct from sibling tools that handle patches and sessions.

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 is provided on when to use this tool versus alternatives. While the siblings are clearly different actions, the description does not mention specific scenarios, prerequisites, or context for invocation.

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