Get instance tree

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't need to cover safety. It adds the behavioral trait that the hierarchy is depth- and breadth-bounded, which is valuable context for what results to expect. However, it doesn't describe truncation behavior or errors.

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?

One sentence, 12 words, front-loaded with the core action and parameters. Every word contributes; no 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 the core purpose and the bounding constraints, but with no output schema, it leaves the return structure undefined. Error behavior and parameter nuances (e.g., defaults) are also omitted. For a 4-param tool, this is adequate but has gaps.

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 low (25%); only clientId has a description. The description only hints at the root parameter ('below any Roblox instance') and does not explain maxDepth/maxChildren semantics beyond their names. It does not compensate for the missing schema descriptions.

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 uses a specific verb ('Return') and resource ('hierarchy below any Roblox instance'), with clear scope ('depth- and breadth-bounded'). This distinguishes it from sibling tools like inspect_instance (single instance) or query_instances (query-based).

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 guidance on when to use get_tree vs alternatives like query_instances or inspect_instance. There are no exclusions or alternative recommendations. The description only implies the use case of fetching a subtree, but doesn't clarify when to prefer this tool.

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