unity_search_assets

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Uses Unity's AssetDatabase search' without mentioning side effects, performance, or safety (e.g., read-only). There is no indication of what happens on empty results or potential cost.

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 sentences with no wasted words. It front-loads the purpose and adds a brief implementation note. Every sentence earns its place.

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?

The tool has 5 parameters and no output schema. The description covers the basic operation but lacks information about return format, pagination, or behavior with no results. Given the sibling tools provide context, it is minimally adequate but not fully complete.

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% with clear parameter descriptions. The description adds 'Uses Unity's AssetDatabase search' which provides context but does not enhance parameter semantics. The schema already explains parameters like 'port' and 'maxResults' well. Baseline 3 is appropriate.

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 verb 'search', the resource 'assets', and the criteria 'by name, type, and folder'. It distinguishes from sibling tools like unity_search_by_name, which are more specific. The phrase 'Uses Unity's AssetDatabase search' adds context.

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 does not explicitly state when to use this tool versus alternatives such as unity_search_by_name or unity_search_by_type. It implies general asset search but lacks guidance on exclusions or preferences. Context is limited to 'Uses Unity's AssetDatabase search'.

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