Find GameObjects

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context by stating the operation is paginated and by describing the return shape.

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 front-loaded with the purpose and constraint, then gives compact examples and a return-shape summary. Every element is useful and there is no filler.

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?

It helpfully covers the search intent, filter examples, pagination, and return fields despite there being no output schema. However, it does not resolve the critical gap that the input schema defines no filter or pagination parameters, leaving invocation details incomplete.

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 description references filter parameters (name_contains, tag, with_component) and says at least one is required, but the input schema exposes zero parameters. This mismatch prevents an agent from knowing how to pass filters or pagination inputs correctly.

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 gives a specific verb and resource: search GameObjects by name substring, tag, or component type. This clearly distinguishes it from siblings like unity_get_hierarchy or unity_get_object_info, which retrieve rather than search.

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 states that at least one filter is required and provides filter examples, which gives some usage context. However, it does not explain when to use this tool instead of alternatives such as unity_get_hierarchy or unity_get_scene_info.

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