audio_component_add

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

With no annotations, the description carries the burden. It discloses that the tool 'Compiles and saves' the blueprint, which is a key side effect, and notes that asset assignment and auto-activate are optional. However, it does not explain behaviors such as overwriting existing components or failure modes, leaving some transparency gaps.

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 two short sentences, front-loaded with the action and no filler. Every phrase adds value, making it appropriately concise.

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?

The tool has 5 parameters and no output schema, and the description covers the main operation and side effects but omits details like prerequisites, error behavior, or what the return value is. Given the moderate complexity and lack of annotations, the description is adequate but not fully complete.

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 covers 4 of 5 parameters (80%), and the description echoes 'optional' for sound and auto_activate. It adds little beyond the schema, such as clarifying blueprint_path, so the parameter semantics are adequately but not richly conveyed.

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 ('Add') with a clear resource ('AudioComponent to a Blueprint'), and mentions optional asset assignment and auto-activate. This distinguishes it from sibling tools like blueprint_component_remove or blueprint_node_add, making the tool's purpose unambiguous.

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 states what the tool does but does not explicitly say when to use it or provide exclusions. The context implies it is for adding audio components, but no alternative tools are mentioned, so the agent must infer usage from the name and sibling list.

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