Set audio sync offset

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

With no annotations, the description carries the full burden and does provide the key behavioral trait that positive delays and negative advances audio. However, it omits other behavioral details such as persistence, source type restrictions, or side effects on existing settings, so it only partially discloses behavior.

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 two short sentences, front-loaded with the core action, and every phrase contributes (units, sign semantics). It is concise without missing essential information.

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 simple two-parameter setter with an output schema, the description adequately covers the operation and parameter meaning. It does not explain prerequisites for source types or error behavior, but these are likely covered by the output schema and the tool's simplicity reduces the need for extensive context.

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. It explicitly defines offset_ms as milliseconds and gives meaning to positive/negative values, while source_name is implied as the target source. This adds meaningful semantic value beyond the bare schema fields.

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 uses a specific verb 'Set' and names the resource 'audio sync offset', clearly distinguishing it from sibling tools like set_volume or set_audio_monitor. It also states the scope 'for a source' and the unit 'milliseconds', making the purpose unambiguous.

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 description implies the tool is used to adjust audio sync offset by stating the action and sign semantics, giving clear context. It does not explicitly mention when to prefer this over alternatives or list exclusions, but the context is sufficient for an agent to infer appropriate use.

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