game_get_audio

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

The verb 'Get' implies read-only behavior, but without annotations like readOnlyHint, the description does not confirm this or disclose any other behavioral traits (e.g., performance impact, permissions).

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?

A single, clear sentence with no wasted words. It front-loads the action and resource effectively.

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 zero parameters and no output schema, the description is minimal but functional. It lacks details on return format or side effects, but may be sufficient for a simple query tool.

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?

No parameters are defined, so the schema coverage is 100%. Per guidelines, baseline is 4; the description does not need to add parameter details.

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 the tool gets 'audio bus layout and playing streams' with a specific verb and resource. However, it doesn't explicitly differentiate from sibling tools like 'game_audio_bus_layout' or 'game_audio_play', but the combined phrasing suggests a broader retrieval.

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 such as 'game_audio_bus_layout' or 'game_audio_play'. The occurrence context is implied but not explicit.

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