unity_search_assets

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

No annotations are provided, so the description carries the full burden. It discloses that the search uses Unity's AssetDatabase and accepts multiple filters, but doesn't mention performance characteristics, whether it's read-only, or any side effects. The behavioral info is adequate but not comprehensive.

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, efficient and to the point. It front-loads the purpose and then mentions the underlying API. Every sentence adds 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?

Given 5 parameters, no output schema, and no annotations, the description is somewhat sparse. It doesn't explain what the output looks like, how results are sorted, or the behavior when no results are found. It's minimally complete but lacks detail for a robust agent decision.

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 100%, so the schema already documents all parameters. The description provides a high-level overview (name, type, folder) but adds no additional semantics beyond what the schema gives. For example, it doesn't explain the behavior of combining filters or default maxResults. 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 it searches for assets by name, type, and folder, and mentions using Unity's AssetDatabase. It distinguishes from siblings like unity_search_by_name, unity_asset_list, and unity_search_by_type by combining multiple filters.

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 vs alternatives like unity_search_by_name or unity_asset_list. It implies usage by mentioning multiple search criteria, but lacks guidance on trade-offs or scenarios.

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