Unity AI Bridge

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 creation but doesn't disclose behavioral traits like whether it requires specific permissions, if it overwrites existing files, error handling, or what happens upon success (e.g., does it open the scene?). This leaves significant gaps 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?

It's appropriately sized with two concise sentences that are front-loaded: the first states the core action, and the second provides a useful follow-up tip. Every sentence earns its place without waste.

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 no annotations and no output schema, the description is minimal but covers the basic action. It hints at post-creation behavior with the sibling tool reference, but for a mutation tool with 3 parameters, it lacks details on permissions, errors, or return values, making it only adequate.

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 fully documents all parameters. The description adds no additional meaning beyond what's in the schema (e.g., no extra context on path formatting or enum implications), meeting the baseline for high 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 action ('Create new scene') and resource ('in the project assets'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'scene-open' or 'scene-save', which also involve scene operations.

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?

It provides clear context by mentioning to use 'scene-list-opened' after creation, which implies this tool doesn't automatically list scenes. But it lacks explicit guidance on when to use this versus alternatives like 'scene-open' or 'scene-save', or any prerequisites.

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