uad_talkback

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

With no annotations, the description carries the transparency burden. It discloses the auto-off timer default of 30 seconds and that 'Calling it again replaces the timer.' This is useful behavioral context beyond simple on/off. However, it doesn't mention the return value or any other side effects, which would make it fully transparent.

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 concise and well-structured: an opening sentence with core behavior and timer safety, followed by clear 'Use when' and 'Not for' sections. Every sentence adds value without repetition or fluff.

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 three optional parameters and an output schema. The description covers purpose, usage, exclusions, and parameter semantics. It lacks edge-case details (e.g., what happens when 'on' is null, or level ranges), but these are not essential for a basic invocation, making it reasonably 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?

Schema coverage is 0%, so the description compensates by explaining the semantic meaning of each parameter: 'on' maps to 'Turn talkback on or off', 'level' to 'set its level', and 'auto_off_s' to the auto-off timer. It doesn't specify units or valid ranges for level, but the functional purpose is clear enough for invocation.

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's function: 'Turn talkback on or off and set its level, with an auto-off timer.' It also distinguishes the tool from routing tasks by explicitly saying 'Not for: routing the talkback mic or choosing which mic it is - that is set in Console.' This sets it apart from sibling tools like uad_set_sends.

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?

Provides explicit guidance: 'Use when: the engineer needs to speak to the live room.' and 'Not for: routing the talkback mic or choosing which mic it is.' This clearly outlines when to use and when not to use, with an alternative context ('set in Console').

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