play_audio

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

With annotations provided, the description adds useful behavioral context beyond the safety flags: it discloses the 30-second maximum, local-only file behavior, and platform-specific conversion via afconvert or ffmpeg. It does not explain failure behavior for oversized files or unsupported formats, but it adds meaningful operational detail.

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 short and front-loaded with the primary action and constraint. The platform conversion detail and local-only warning are compact and relevant, with no wasted sentences.

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 one-parameter playback tool with annotations and no output schema, the description covers the essential constraints: local file, speaker target, duration limit, and no remote fetching. It is mostly complete, though the path parameter could be described more precisely.

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 path parameter has 0% schema description coverage, so the description must compensate. It clarifies that the file is a local controller audio file and that remote URLs are not fetched, but it does not specify path format, expected location, or supported audio formats.

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 states a specific verb and resource: playing a local controller audio file on the AIY speaker, with a 30-second limit. It is clear about what the tool does, but it does not explicitly contrast itself with sibling tools such as speak or speak_on_echo.

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 implied usage constraints: the file must be local, no remote URLs are fetched, and playback is capped at 30 seconds. However, it does not explicitly say when to use this instead of speak, speak_on_echo, or other audio-related siblings.

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