Tuanjie Editor Controller

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

The annotations already mark destructiveHint=true, and the description adds little behavioral context beyond the list of action names. The pass-through note about action-specific parameters is mildly useful, but the description does not explain side effects, compilation behavior, editor state changes, or what agents should be cautious about given the destructive hint.

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 a clear opening, but most of it is a 28-item action list that duplicates the schema enum. This is not an efficient use of the description and pushes out room for more useful behavioral or parameter documentation.

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?

For a 28-action dispatcher with no output schema and no per-action parameter documentation, this description is grossly incomplete. It does not tell agents what any action returns, which actions are destructive, when compilation is needed, or how to invoke even common actions like play or set_active_tool correctly.

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 0%, and the description only repeats the action enum and says additional action-specific parameters are passed through unchanged. This gives agents no meaningful detail about what parameters each action expects, how to format them, or which ones are required for specific actions.

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 opening phrase 'Controls and inspects the Tuanjie Editor' states a clear verb and resource, and the tool is reasonably distinguished from sibling tools by targeting the editor itself. However, the purpose is extremely broad because it is a 28-action dispatcher, and the description does not clarify what each action accomplishes.

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?

There is no guidance about when to use this tool versus the many specific sibling tools such as unity_gameobject, unity_scene, or unity_script. The description neither states exclusions nor recommends this tool for particular workflows, leaving the agent to infer usage solely from the action names.

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