unity_list_advanced_tools

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

The description explains that tools are not directly exposed but callable via another tool, and mentions categorization. Since no annotations are provided, this adds value, but could further clarify if the list is dynamic or static.

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 concise, with two sentences covering purpose, organization, and category examples. No fluff; each sentence is valuable.

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, the description adequately explains what the tool returns (list of tools by category). It could mention whether the list includes descriptions or just names, but overall sufficient for a listing tool.

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 does not reiterate parameters since schema coverage is 100%, but it adds context for the 'category' parameter by listing examples. The 'port' parameter is also explained in context of parallel-safe routing, which adds meaning beyond 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 lists advanced/specialized Unity tools organized by category, and that they can be called via unity_advanced_tool. It also lists many categories, distinguishing it from siblings like unity_advanced_tool and other listing tools.

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 implies usage for discovering advanced tools and mentions filtering by category, but does not explicitly state when not to use it or provide alternatives. However, it does indicate the relationship with unity_advanced_tool.

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