godot_get_audio_layout

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that it returns the 'complete' hierarchy and includes effect chains, which gives some context about the result scope but does not disclose additional behavior beyond what annotations imply. With strong annotation coverage, a baseline of 3 is appropriate.

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 extra words. It efficiently conveys the core purpose and scope without repetition or unnecessary detail.

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 there is an output schema (so return values are documented), a single boolean parameter with a schema description, and annotations covering safety, the description is complete enough for an agent to call correctly. It lacks explicit usage guidance, but for a simple read-only query tool, the description suffices. A small deduction for not mentioning when to use this over modification tools.

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 a single parameter 'include_effects' with a clear description ('Whether to include effect chain details for each audio bus'), so the schema already handles parameter meaning. The tool description does not add anything about the parameter, but it is not required to. Baseline 3 is given because the schema covers it fully.

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 states a specific verb ('Query') and a clear resource ('complete AudioServer bus hierarchy and effect chains'). This clearly distinguishes it from sibling tools like godot_configure_audio_bus (which modifies) and godot_set_bus_effect (which sets effects on a bus). An agent can immediately understand this is an inspection tool for audio layout.

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 verb 'Query' implies it is for inspection, but the description does not explicitly mention when to use it versus modification tools like configure_audio_bus. There is no alternative routing or when-not guidance. The purpose is clear, but the usage context is implied rather than stated, which is adequate but not explicit.

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