set_input_audio_sync_offset

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

No annotations are provided, so the description bears the full burden. It discloses the operation, the offset range, and the purpose, but does not mention potential side effects, error conditions, persistence, or whether permissions are required. This is adequate but not rich.

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 sentences plus a compact Args list. It front-loads the purpose, then clearly documents parameters. No filler or redundant 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 setter with two primitive parameters and no output schema, the description is mostly complete. It covers what the tool does, when to use it, and parameter semantics. It could additionally mention the companion getter or error behavior, but the tool is straightforward.

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 schema has 0% description coverage, so the description compensates by defining both parameters: 'input_name: Name of the input' and 'offset_ms: Offset in milliseconds, range -950..20000'. This adds meaning beyond the schema's type-only definitions, including a useful range constraint.

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 and resource: 'Set an input's audio sync offset', and adds the purpose 'use to fix audio/video drift'. This clearly distinguishes the setter from the sibling getter (get_input_audio_sync_offset) and other input-related tools.

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 gives a clear usage context: 'use to fix audio/video drift'. It implies an alternative (the getter) but does not explicitly name it or state when not to use this tool. The guidance is present but not exhaustive.

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