unity_scene_hierarchy

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

Discloses dense output (omitting default values) and timeout mitigation via maxNodes. No annotations, so description carries burden; additional details like performance or empty scene behavior could improve transparency.

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?

Two sentences: first states purpose, second explains density. Every sentence adds value, no fluff, front-loaded.

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?

Covers key aspects: hierarchy tree, components, children, dense output, parameter hints. Lacks explicit return format (tree structure), but sufficient given no output schema.

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?

Adds significant meaning beyond schema: explains 'dense by default' for verbose, timeout avoidance for maxNodes, and subtree exploration for parentPath. Schema coverage is 100%, but description enriches.

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 'Get the hierarchy tree of all GameObjects in the active scene, including their components and children,' with a specific verb and resource. It distinguishes from siblings like unity_scene_info and unity_gameobject_info.

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?

No explicit when-to-use or when-not-to-use guidance. The description implies usage for exploring hierarchy and handling large scenes via maxDepth and maxNodes, but does not mention alternatives.

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