uad_get_inserts

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

The description implies a read-only operation but does not disclose key behavioral traits such as the effect of the 'loaded_only' parameter (which defaults to true and likely filters to only loaded slots, contradicting the claim of showing 'every insert slot'). It also omits information about permissions, side effects, or output formatting, and no annotations are provided to compensate.

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 concise and well-structured: two sentences that front-load the purpose and then provide usage guidelines with clear 'Use when' and 'Not for' sections. It is easy to parse and free of unnecessary words, though slightly more detail on parameters would improve it.

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 4 parameters, no schema descriptions, and no annotations, the description should provide substantial guidance. While it gives a general sense of the tool's purpose and usage, it omits crucial details about parameter behavior and output interpretation, making it incomplete for reliable invocation.

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 descriptions are completely absent (0% coverage), and the description adds only a vague hint about selecting 'one channel or all of them'. It does not explain the individual parameters (kind, device, target, loaded_only), leaving the agent without sufficient information to correctly populate them.

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's function with a specific verb ('Show') and resource ('insert slots' plus 'Unison slot'), and details the output content (plugin name, power state, preset). It explicitly distinguishes itself from the sibling tool uad_get_plugin_params by stating it is 'Not for parameter values inside a plugin'.

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 explicit use cases ('Use when: auditing a channel's processing chain or finding a free slot') and a clear exclusion with an alternative tool ('Not for: parameter values inside a plugin - use uad_get_plugin_params'). This gives the agent strong guidance on when to select this tool.

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