Get the descendants tree of a Roblox instance

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

No annotations provided, so description carries full burden. It mentions depth-limiting but does not explicitly state that the tool is read-only or non-destructive. For a retrieval tool, this is adequate but could be more transparent about side effects. Schema coverage is high, but behavioral traits beyond the basic operation are not disclosed.

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 concise sentences, front-loaded with purpose and sibling differentiation. No unnecessary words or repetition. Every sentence adds value.

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 the tool's simplicity (4 parameters, high schema coverage, no output schema), the description is mostly complete. It covers purpose and usage guidelines. It could mention the return format (tree structure) but is not critical. The sibling distinction adds context.

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 description coverage is 100%, so the schema already documents all parameters well. The description does not add significant parameter-specific information beyond the general purpose. It mentions 'depth-limited' which relates to maxDepth, but otherwise relies on 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?

Description clearly states it retrieves a depth-limited hierarchy of descendants, with specific verb ('Get') and resource ('descendants tree'). It distinguishes itself from sibling tool 'search-instances' by noting the use case for broad structure exploration.

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 tells when to use this tool ('for broad structure exploration') and when to use the alternative ('use search-instances for selector-based filtering'). This provides clear guidance on tool selection.

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