agents-voice

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

With no annotations, the description carries the full burden. It usefully discloses the core side effect (audio is spoken directly into the user's ears, so the text is heard not returned), but says nothing about auth/config prerequisites, latency/blocking behavior, or what happens if no TTS provider is configured.

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?

Front-loaded with the action and the when-to-use rule, followed by a compact Args block. The Args section partly echoes schema titles but earns its place by adding examples and the provider list.

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?

An output schema exists so return values need not be explained, and the description covers purpose, timing, formatting constraints, and every parameter. The only real gap is failure/configuration behavior for a tool whose whole job is an external side effect.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it labels all four parameters and supplies concrete example values for message, provider (full list of accepted providers), model, and voice. It notably enumerates provider names that the schema does not constrain via an enum.

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 ('Speak a short, natural voice summary') plus scoping constraints (1-2 sentences, to the user's ears). An agent immediately understands this produces audio output rather than text, which distinguishes it from the read-only voice_status sibling by name and role.

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?

Explicitly says when to use it ('at the end of substantive turns to tell the user what was done') and gives a clear exclusion ('without reading code, diffs, or markdown formatting'). It does not mention voice_stop or voice_status as alternatives or when to avoid speaking, so the routing picture is incomplete.

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

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

No annotations exist, so the description carries the disclosure burden. It does reveal the scope of inspection (provider, keys, bridge), which implies a non-mutating check, but it never states that the operation is read-only, side-effect free, or what a failed/unconfigured state looks like.

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 front-loaded sentence with no filler. Every listed item (provider, keys, bridge) is substantive and none is redundant.

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?

An output schema exists, so the description need not enumerate return values, and the tool is simple (0 params, no nesting). What remains missing is a short note on when to reach for it, but for a trivial status endpoint this is close to sufficient.

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 no parameter semantics are needed. The description sensibly spends its words on what the no-arg call reports rather than inventing arguments.

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 ("Checks") and resource ("status of the voice output system") and enumerates what is inspected: active provider, configured keys, and bridge. It is clearly a read/diagnostic tool separable from the mutating siblings voice_speak and voice_stop, 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?

No when-to-use guidance is provided. The description does not say to run this before voice_speak to verify configuration, nor does it mention any precondition, failure mode, or alternative. The diagnostic intent is only implied by the word "status."

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

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: the stop is immediate and scoped to 'currently playing' audio, implying a no-op when nothing is playing. It says nothing about whether the operation is interruptible, resumable, or safe to call repeatedly, which leaves real gaps for a zero-annotation 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?

A single front-loaded sentence with the verb and immediacy first and the trigger condition last; no filler or redundant restatement of the title.

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?

Output schema exists, so return values need no explanation, and there are no parameters to document. For a simple stop command the description covers the essentials, missing only edge-case behavior.

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 no parameters, so there is nothing for the description to clarify and no schema gap to compensate for. Baseline for a zero-parameter 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?

States a specific verb (stops) and resource (currently playing speech audio) with an immediacy modifier, so the effect is unambiguous. Siblings voice_speak and voice_status make the domain obvious, though the description never explicitly contrasts itself with them.

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?

"if the user requests silence" gives a trigger condition for use, which is more than most zero-param tools offer. It stops short of naming alternatives (e.g., pausing vs stopping) or stating when not to call it.

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