Unity AI Bridge

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

No annotations are provided, so the description carries full burden. It mentions the context ('prefab editing mode') but lacks critical behavioral details: whether this is a destructive operation (overwrites existing prefab), requires specific permissions, has side effects, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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 two concise sentences with zero waste: the first states the purpose, and the second provides essential usage guidelines. It's front-loaded with the core action and efficiently includes only necessary context, making it easy to parse.

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 has 0 parameters, no output schema, and no annotations, the description provides adequate basic context (purpose and prerequisites). However, as a mutation tool ('save'), it lacks details on behavioral outcomes, error conditions, or what 'save' entails operationally, leaving gaps for an agent to invoke it correctly in edge cases.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on usage context. A baseline of 4 is applied since the schema fully handles parameters, and the description adds value elsewhere without redundancy.

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 ('Save a prefab') and resource ('prefab'), making the purpose understandable. It distinguishes from siblings like 'assets-prefab-create' or 'assets-prefab-open' by focusing on saving rather than creating or opening. However, it doesn't specify what 'save' entails (e.g., overwriting existing, creating new version), which prevents a perfect score.

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 explicitly states when to use it ('when you are in prefab editing mode in Unity Editor') and provides a prerequisite alternative ('Use 'assets-prefab-open' tool to open a prefab first'). This gives clear context and distinguishes it from other prefab-related tools, making it highly actionable.

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