game_audio_spatial

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

No annotations are present, so the description must fully disclose behavior. It only states 'Configure AudioStreamPlayer3D spatial properties', omitting that the tool also supports a 'get_info' action and does not explain side effects, permissions, or error handling. The description is misleading by implying it is only for configuration.

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 short sentence, which is concise and easy to read. However, it could be longer to include more detail without sacrificing clarity. It is front-loaded with the key verb and resource.

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 has 6 parameters and no output schema, the description is very sparse. It does not explain how the parameters interact, what the configuration does, or how to interpret results. The schema fills in some gaps, but overall context for effective use is lacking.

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 has 100% description coverage, with each parameter including a brief description. The tool description adds no additional meaning beyond what is already in the schema, so the baseline score of 3 is appropriate.

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 specifies the action 'Configure' and the resource 'AudioStreamPlayer3D spatial properties', clearly indicating the tool's domain. However, it does not mention that the tool also supports a 'get_info' action, which is present in the schema, so the purpose is partially accurate but not fully comprehensive.

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 is provided on when to use this tool versus sibling audio tools like 'game_audio_play' or 'game_audio_bus'. There is no mention of prerequisites, alternatives, or typical scenarios for using this tool.

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