game_audio_play

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

Description indicates mutability (play/stop/pause) but fails to disclose side effects, error states, or behavior for missing nodes. The action 'resume' is in the schema but not mentioned. No annotations compensate.

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?

Single sentence is concise but the tool handles 7 parameters and 4 actions; the brevity omits critical context, so it doesn't fully earn its place.

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?

With 7 parameters and no output schema, the description is too minimal. It doesn't cover use cases, ordering, or combinations of actions (e.g., loading stream while playing).

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 coverage is 100% with descriptions for all 7 parameters, so baseline is 3. The description adds no extra meaning beyond restating the tool's function; it doesn't clarify parameter interactions or defaults.

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 'Play, stop, or pause an AudioStreamPlayer node' clearly states the action and resource, distinguishing it from sibling audio tools like game_audio_bus or game_audio_effect.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or when-not-to-use conditions. Among many audio-related siblings, this lack of context hinders correct selection.

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