bip_play_timeline

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

With no annotations, the description carries the full behavioral burden, and it only discloses that playback is non-blocking. It does not say whether the timeline replaces the current facial state, what happens if playback is already running, whether keyframe times are relative to invocation, or how errors and completion are surfaced.

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?

One tightly written sentence with no filler, and the essential purpose is front-loaded. Its brevity is efficient but contributes to the missing detail elsewhere.

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?

This is a structurally complex tool — a required array of keyframe objects — with no annotations and no output schema, so the description should explain keyframe field meaning and playback lifecycle. Instead it covers only the high-level intent and one execution trait, leaving an agent unable to construct a valid, meaningful keyframe list confidently.

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 single keyframes parameter has 0% schema description coverage and a nested object with six undocumented subfields (at_ms, state, blink, gaze_x, gaze_y, speaking). The phrase "time-coded" implies at_ms semantics, but state values, gaze coordinate ranges, and units are left entirely unexplained.

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 names a specific verb ("Play") and a specific resource ("a sequence of time-coded facial animation keyframes on BIP"), so the agent understands this schedules an animation timeline rather than a one-shot state change. It stops short of explicitly contrasting itself with bip_set_state or bip_speak, so the differentiation is inferred rather than stated.

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?

There is no guidance on when to choose a timeline playback over bip_set_state or bip_speak, and no mention of prerequisites such as connecting to the device first. The parenthetical about a non-blocking firmware loop is the only hint about invocation context.

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