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 and discloses key behavioral traits: it modifies the project's manifest.json, triggers package resolution and domain reload, and indicates that results are sent after reload completion. This covers mutation effects and operational behavior, 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 appropriately sized and front-loaded, starting with the core action, followed by operational details and sibling tool references, with every sentence adding value and no wasted words.

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 complexity of a package installation tool with no annotations and no output schema, the description is fairly complete, covering purpose, usage, behavioral effects, and parameter context. It could be more complete by detailing output or error cases, but it provides sufficient guidance for basic use.

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 50% (only packageId has a description), and the description adds meaning by explaining the installation sources (registry, Git URL, local path) and mentioning package resolution, which provides context beyond the schema. However, it doesn't detail the requestId parameter.

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 ('Install a package') and resource ('from the Unity Package Manager registry, Git URL, or local path'), distinguishing it from sibling tools like 'package-search' and 'package-list' by specifying installation versus searching or listing.

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 explicitly provides when to use this tool ('Install a package') and when to use alternatives ('Use 'package-search' tool to search for packages and 'package-list' to list installed packages'), offering clear guidance on tool selection.

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