import_asset_to_project

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates the local-only restriction and the project_dir root requirement, but it does not state whether existing files in Assets/ will be overwritten, merged, or left untouched if a conflict occurs. For a mutating operation that unpacks into a project filesystem, that is a notable omission.

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?

Three focused sentences with no filler. The primary action is front-loaded, followed by the eligibility precondition and the critical project_dir requirement. Every sentence adds operational value.

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?

For a two-parameter tool with an output schema, the description covers the core action, the target location, the eligibility requirement, and the directory root expectation. The main missing context is conflict/overwrite behavior, but the definition is otherwise sufficient for an agent to invoke the tool correctly in the common case.

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% property description coverage, so the description must compensate. It explains project_dir clearly, but asset_id is left implicit as 'the package to unpack' with no guidance on its format, source, or relationship to search results. This leaves one of two required parameters essentially undocumented.

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 uses a specific verb ('Unpack') and a clear resource/goal: importing a locally-downloaded .unitypackage into a Unity project's Assets/ folder. This clearly differentiates it from the sibling search, audit, and recommendation tools.

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 states the precondition 'Only works for assets tagged local=true (check with search first)', directing the agent to verify eligibility using a sibling search tool. This provides clear when-to-use guidance and implies the alternative when the condition is not met.

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