unity_asset_list

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

No annotations are provided. The description does not disclose behavioral traits such as default recursive scanning, performance impact of large projects, or that listing covers the entire 'Assets' folder by default. The parameter descriptions hint at limits, but the overall behavior is under-specified.

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?

Extremely concise—two sentences that immediately convey the purpose. No redundant words or unfocused content. Ideal front-loading.

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?

Despite full schema coverage, the description lacks context about return format, default behavior (e.g., recursive true, maxResults default 500), and no output schema exists. A tool with 6 parameters and multiple filters needs more behavioral and result context.

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 coverage is 100%, so each parameter is well-described in the schema. The description adds minimal extra meaning beyond the schema (e.g., 'Can filter by path, type, and search term'). Baseline of 3 is appropriate since schema does most of the work.

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?

Clearly states 'List assets in the project' and mentions three filter types. However, it does not explicitly differentiate from sibling search tools like unity_search_assets, unity_search_by_name, etc., which could cause confusion.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., unity_search_assets or unity_search_by_name). The description implies general asset listing but lacks explicit when-to-use or when-not-to-use instructions.

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