unity_advanced_tool

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

With no annotations, the description bears full burden. It mentions caching and lazy loading but fails to disclose potential destructive actions, required permissions, or error behavior. The generic executor nature introduces risk without warning.

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 sentence that packs essential information. It is front-loaded with the action and resource. Slightly ambiguous phrasing ('parameters via tool=') costs a point.

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?

Despite the complexity and lack of output schema, the description omits return value, error handling, and safety warnings. The 'advanced' concept remains undefined, and caching details are unclear.

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%, providing baseline of 3. The description adds value by instructing how to obtain tool names and parameter structures via unity_list_advanced_tools, which is not in the schema.

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 tool executes an advanced Unity tool by name, with specific instructions on discovering tool names via unity_list_advanced_tools. This differentiates it from sibling tools that are specific tool names.

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 explicitly tells how to discover tool names and parameters via unity_list_advanced_tools. It implies using this tool for advanced tools not covered by dedicated MCP functions, but does not state when not to use it.

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