unity_list_advanced_tools

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

No annotations are provided, so the description carries full burden. It discloses that tools are not directly exposed and can be called via unity_advanced_tool, which is useful. However, it does not mention whether the tool is read-only, performance considerations, or the structure of the output.

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, fitting in a single paragraph. It front-loads the main purpose and provides a comprehensive list of categories. Every sentence contributes meaning without redundancy.

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?

The description covers purpose and category usage but lacks details on the output format (e.g., list of tool names, objects, or IDs) and any potential limits. Given the tool's simplicity and lack of output schema, a brief note on return type would improve completeness.

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%, so baseline is 3. The description adds value by listing many category examples (animation, shadergraph, etc.), which clarifies the filter parameter beyond the schema's generic description. The port parameter is already well-described 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 it lists advanced/specialized Unity tools by category, and distinguishes from siblings by noting these tools are not directly exposed but callable via unity_advanced_tool. The verb 'list' is specific and the resource is well-defined.

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 provides clear context for when to use the tool (to list available advanced tools) and mentions the related tool unity_advanced_tool for execution. It does not explicitly state when not to use it, but the categorization guidance is helpful.

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