Unity AI Bridge

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. It effectively reveals that the tool performs AssetDatabase.Refresh() automatically after copying, which is a critical behavioral trait not inferable from the schema. It also implies a write operation through 'copy' and 'stores,' though it could mention permissions or error handling.

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 front-loaded with the core functionality in the first sentence and adds a usage tip in the second. Both sentences earn their place by providing essential information without redundancy, making it appropriately sized and 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 complexity (a write operation with two parameters), no annotations, and no output schema, the description is mostly complete. It covers purpose, behavior, and usage, but could improve by mentioning error cases or the lack of output details, which would help an agent handle responses better.

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 100%, so the schema already documents both parameters thoroughly. The description does not add any parameter-specific semantics beyond what the schema provides, such as format details or constraints, meeting the baseline for high schema coverage.

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 specific action ('Copy the asset at path and stores it at newPath') and identifies the resource ('asset'), distinguishing it from sibling tools like assets-move or assets-duplicate. It provides a complete verb+resource+outcome statement.

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 includes explicit guidance to 'Use assets-find tool to find assets before copying,' which provides clear context for when to use this tool. However, it does not specify when NOT to use it or mention alternatives like assets-duplicate for game objects, leaving room for improvement.

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