waiting_on_refresh_voice

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

Reveals observe-only nature, which is important for behavior. However, without annotations, the description lacks detail on what 'refresh' entails (e.g., triggers server-side processing, side effects), leaving ambiguity.

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?

Single sentence that packs key info (action, resource, format, read-only) with no wasted words.

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?

Adequate for a zero-parameter tool, but lacks explanation of what 'open loops' are, the event log's role, or typical use cases, leaving some gaps for an agent.

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?

No parameters in schema (100% coverage), so description adds no param info—appropriate baseline as there is nothing to document.

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?

Clear verb 'refresh' and specific resource 'voice-queue open loops', with parenthetical clarification 'JSONL event log; observe-only' that distinguishes it from siblings like 'waiting_on_refresh' or 'waiting_on_loops'.

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 explicit guidance on when to use this tool versus siblings like 'waiting_on_refresh', 'waiting_on_loops', or 'waiting_on_show'. The 'observe-only' hint is implicit, but not enough to differentiate usage context.

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