list_speakers

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

With no annotations, the description carries the full burden; "Show" implies a safe read but this is never stated outright. It does add useful behavioral context by naming the TTS_OUTPUT configuration knob, but it says nothing about failure modes (e.g. no audio device present) or the shape of the returned speaker list.

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?

A single sentence with the main purpose front-loaded and the remedial hint tucked into a parenthetical. No filler, no repetition of the tool name, nothing to trim.

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 tool with no output schema, the description covers what is listed, which entry is the active one, and how to change it. The only gap is the return format, which is implied rather than stated and is minor at this complexity.

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 takes zero parameters, so the baseline is 4 and there is no parameter meaning to compensate for. The TTS_OUTPUT mention describes external configuration rather than an argument, which is still helpful orientation.

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?

States a specific verb and resource ("Show the PC speakers") and adds scope, namely that it also reports which speaker voice output plays through. It is distinguishable from list_microphones and list_devices by the audio-output framing, though it never names those siblings explicitly.

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 parenthetical "set TTS_OUTPUT to change" tells the agent what to do when the desired speaker is not active, which is genuine routing guidance. It gives no explicit when-to-use vs list_devices or list_microphones and no conditions under which calling it is unnecessary.

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