inspect_producer_bus

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it reports mismatches, performs no edits, and inspects specific aspects (ordered bus FX, child identities, group membership, output routing). This goes beyond the annotations and helps the agent understand what the tool will and won't do.

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?

Two sentences, no filler. The first sentence states the resource and scope; the second states the outcome and the non-destructive nature. Every clause earns its place.

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 read-only inspection tool with no output schema, the description covers what is inspected and the fact that mismatches are reported. It doesn't describe the exact report format or how mismatches are represented, but given the tool's read-only nature and the annotations covering safety, this is a minor gap. The description is complete enough for an agent to decide when to call it.

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 67%: busTrackId and children have descriptions, but target only has an enum with no description. The description explains the overall purpose and mentions 'blueprint' and 'child roles', which helps interpret target and children, but it doesn't add detail about how target maps to a blueprint or how children should be structured beyond what the schema already says. Baseline 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 uses a specific verb ('Read') and names the exact resource ('existing Group Track, its ordered bus FX, child instrument identities, group membership and actual output routing') and the comparison target ('one layered-system blueprint'). It also states the outcome ('Reports mismatches without edits'), which clearly distinguishes it from sibling tools like inspect_producer_chain or set_master_mixer.

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 implies when to use it: when you need to verify a group track against a layered-system blueprint and detect mismatches. It does not explicitly name alternatives or state when not to use it, but the read-only, inspection-oriented wording and the mention of 'blueprint' provide clear context. A small gap: it doesn't explicitly say 'use inspect_producer_chain for X instead'.

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