remove_meta_data

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

No annotations are provided, and the description gives no warnings about the destructive nature of removing metadata, nor any side effects or permission requirements. It simply restates the action without behavioral context, leaving the agent unaware of the irreversibility or the impact of removing all metadata.

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, front-loaded with the main action, and includes only essential parameter documentation. No unnecessary wording.

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 relative simplicity, the description covers the basics but lacks critical context about consequences of removal, output, or when to prefer other tools. The presence of an output schema doesn't compensate for missing usage and behavior guidance, especially for a destructive operation.

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 description adds brief explanations for both parameters, clarifying that 'meta_data_class' can be omitted to remove all metadata, which is not fully specified in the schema. However, it lacks detailed semantics about valid classes and the meaning of 'metadata' in the Unreal context.

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 'Remove metadata from an animation asset' with a specific verb and resource, and the parameter 'meta_data_class' clarifies scope. It distinguishes from the sibling 'add_meta_data' by its opposite action.

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 usage by its action verb but does not explicitly state when to use it versus alternatives like 'add_meta_data' or mention prerequisites or exclusions. It is clear that this tool is for removal, but no explicit guidance is given.

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