unity_advanced_tool

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

No annotations provided; description mentions '200+ specialized tools' and categories, and hints at parallel-safe routing via port parameter. It does not disclose error handling, validation, or safety traits, leaving gaps despite the absence of annotations.

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?

Three concise sentences: states purpose, discovery method, and scope. No fluff or redundant information.

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 generic dispatcher with no output schema, description lacks return format, error behavior, and the fact that tool name must be from the list. Adequate but not fully complete for all aspects of usage.

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%; description adds no new meaning beyond schema. It repeats parameter names (tool, params, port) without additional context. Baseline 3 due to full schema coverage, but no extra value.

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?

Description clearly states 'Execute an advanced/specialized Unity tool by name' and distinguishes from sibling tools which are specific tools (e.g., unity_asset_create_prefab). It identifies the tool as a generic dispatcher for advanced operations.

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?

Explicitly instructs to use unity_list_advanced_tools for discovery, providing clear context for when to use this tool. Does not include explicit when-not or alternative exclusions, but the sibling list implies it's for tools not directly exposed.

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