game_audio_spatial

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

With no annotations, the description carries the full behavioral disclosure burden, but it only says 'Configure' and gives no detail on side effects, whether get_info returns data, failure behavior, or whether configuration is applied to an existing node. The tool actually supports a get_info mode, which the description does not reveal.

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 a single, front-loaded sentence with no wasted words. It is concise and names the target resource immediately, though it could have used the spare sentence to mention the get_info action.

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 that this tool has two distinct actions, six parameters, no output schema, and no annotations, a one-line description is insufficient. The agent is not told what get_info returns, what each action does, or what behavioral consequences configuration has on the audio player. The schema covers parameter names but not enough context for correct invocation.

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 description coverage is 100%, so the parameters are already documented in the schema. The description adds little beyond labeling the parameters as 'spatial properties', but it does not need to compensate for missing schema descriptions. It still does not clarify the difference between the configure and get_info actions.

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 resource (AudioStreamPlayer3D) and a specific operation (Configure spatial properties), which clearly distinguishes it from sibling audio tools like game_audio_play and game_audio_bus. However, it omits the get_info action that the schema exposes, so it under-describes the tool's full purpose.

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 about when to use this tool versus alternatives such as game_audio_play, game_audio_bus, or game_audio_effect. The description implies 'spatial audio configuration' but never states when that is appropriate or when it is not.

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