unity_search_by_name

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

Without annotations, the description carries full burden but only mentions 'substring matching or regex' capabilities. No information about whether the search is read-only, performance implications, or what the return data includes (e.g., object references vs. names).

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?

Two short, front-loaded sentences with no superfluous content. However, could incorporate more context (e.g., usage notes) without becoming verbose.

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 description is adequate for a simple search but lacks completeness: no mention of the port parameter's necessity for multi-instance scenarios, no explanation of return format (GameObject names, paths, or references), and no integration hints with sibling tools. Output schema absent, so description could compensate.

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 all parameters described. The description echoes regex support but adds no additional semantics beyond the schema. Baseline of 3 applies as no extra value is provided.

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 'Find all GameObjects whose name contains a pattern' which specifies the action and resource. It also mentions substring and regex support, immediately differentiating it from sibling search tools like unity_search_by_layer or unity_search_by_component.

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?

No guidance is provided on when to use this tool versus the many sibling search tools (by layer, component, tag, etc.). The description implicitly indicates it's for name-based search, but does not explicitly state alternatives or conditions for use.

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