Unity Get GameObject

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

With no annotations, the description carries full burden. It fails to disclose critical behaviors: what happens if the path does not exist (error vs. null), whether the operation is read-only, or timeouts beyond the param. The mutation potential is not clarified.

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 a single, well-structured sentence of 13 words. It is front-loaded with the verb and resource, with no redundancy or waste.

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 no output schema or annotations, the description should hint at return structure and error handling. It does not mention what 'properties' are returned or behavior on missing path. The timeout param suggests potential latency, but no context is given.

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% and descriptions for parameters are present but minimal. The tool description adds context that it 'gets properties', but does not expand on param meanings beyond the schema. Baseline of 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 'Get properties of a specific GameObject by path', specifying the verb, resource, and method. It distinguishes from siblings like unity_get_hierarchy (hierarchy browsing) and unity_create_gameobject (creation), but 'properties' is vague and could be more specific.

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 alternatives such as unity_get_hierarchy for browsing or unity_raycast for spatial queries. The description does not mention prerequisites, exclusions, or comparative scenarios.

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