audio_manage

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

No annotations exist, so the description must disclose behaviors. It mentions that play and stop are editor preview playback and not undoable, but it does not address other behavioral aspects like destructive actions, permissions, or side effects of player_create or player_set_stream.

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 well-structured with a brief purpose line followed by bulleted operations. It is moderately concise; the canonical call shape explanation adds clarity but could be shortened. Overall, it communicates effectively without excessive verbosity.

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?

Given the tool's complexity (multiple ops with diverse parameters), the description covers all operations and their parameters. An output schema exists but is not elaborated; the description only mentions return value for player_set_stream. For most use cases, completeness is adequate.

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 input schema only defines abstract parameters (op, params, session_id). The description adds detailed semantics for each op, including required parameters (e.g., parent_path for player_create), default values (name='AudioStreamPlayer'), and enums (type: '1d'|'2d'|'3d'). This fully compensates for the 0% schema description coverage.

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 that the tool manages audio via AudioStreamPlayer nodes, listing all operations (player_create, player_set_stream, etc.). It distinguishes from sibling tools like node_manage or api_manage by focusing exclusively on audio management.

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 does not explicitly state when to use this tool versus alternatives. Usage is implied by the tool's specific role, but no when-not-to-use guidance or comparison with siblings is provided.

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