add_meta_data

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Add metadata' without revealing whether existing metadata is overwritten, whether the operation is reversible, what happens on duplicate metadata, or any required permissions. This is a significant gap for a mutation tool.

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 short and front-loaded with a clear one-sentence purpose followed by a compact Args block. However, the Args block largely duplicates the input schema, which adds redundant structure without earning its place fully.

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 mutation tool with no annotations, this is incomplete. It does not explain what metadata classes are valid, how metadata interacts with existing asset data, error conditions, or the relationship to sibling tools such as 'remove_meta_data'. The simple two-parameter signature reduces the burden slightly, but key context is still missing.

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 0%, so the description must compensate. It clarifies 'asset_path' as an Unreal asset path, which adds some meaning, but 'meta_data_class: Metadata class name' merely restates the parameter name without explaining valid values, naming conventions, or how the class is resolved.

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 action ('Add metadata') and the target resource ('an animation asset'), using a specific verb and object. It distinguishes itself from the sibling 'remove_meta_data' tool, though it does not elaborate on what metadata types or classes are supported.

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?

No guidance is provided for when to use this tool versus alternatives like 'remove_meta_data' or other add_* tools. There is no mention of prerequisites, common scenarios, or when this tool would be inappropriate.

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