game_get_audio

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

With no annotations, the description carries the full burden of behavioral disclosure. The word 'Get' implies a read-only, non-mutating operation, and the resources being retrieved are named. However, it does not state what the return format is, whether the result is a snapshot or live reference, or any error conditions.

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 concise sentence with no filler. Every word contributes meaning by naming the operation and the returned resources, which is ideal for a zero-parameter getter.

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?

For a zero-input read tool, the description names the high-level output topics and is mostly sufficient. However, there is no output schema and no differentiation from closely named audio siblings, so an agent could pick the wrong tool when multiple audio-related options exist.

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 tool has zero parameters, so there is no parameter ambiguity for the description to clarify. Schema description coverage is effectively 100%, and the baseline for a zero-parameter tool is appropriately 4.

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 verb ('Get') and identifiable resources ('audio bus layout', 'playing streams'), so an agent can understand what the tool does. It doesn't explicitly differentiate itself from sibling tools like game_audio_bus or game_audio_bus_layout, but the purpose itself is clear.

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 provides no guidance about when to use this tool versus related audio siblings such as game_audio_bus, game_audio_bus_layout, or game_audio_play. There is no mention of context, exclusions, or alternatives.

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