ue_create_metasound_source

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

No annotations are provided, so the description carries the full burden. It mentions the plugin requirement and that the asset is empty, but does not disclose error scenarios, whether creation can overwrite existing assets, permissions needed, or if the operation is synchronous. For a creation tool, this is minimal behavioral disclosure.

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: two sentences covering purpose, prerequisite, and next step. It is front-loaded with the main action. However, it could be slightly improved by including parameter details, but overall it is efficient.

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's simplicity (2 parameters, no output schema), the description is incomplete. It fails to clarify what the function returns, whether it's blocking, or what happens if the asset already exists. The post-creation guidance is helpful, but the overall context for an agent is insufficient.

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 two parameters (name and package_path) with defaults and 0% schema description coverage. The description does not reference these parameters at all, providing no additional meaning about what they control or how they affect the creation. This is a significant gap.

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 'Crea un asset MetaSound Source vuoto' (Create an empty MetaSound Source asset), specifying the verb and resource. It distinguishes this from sibling create tools by naming the specific asset type, though it does not explain what a MetaSound Source is or how it differs from other audio assets.

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 a clear next step: 'Il grafo va poi popolato nell'editor MetaSound o via ue_exec_python.' (The graph must then be populated in the MetaSound editor or via ue_exec_python.) However, it does not specify when to use this tool versus alternatives like ue_create_sound_cue, nor does it state any preconditions beyond the plugin requirement.

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