get_descendants

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly defines the scope ('all descendants'), the output content ('classNames and full paths'), and implicitly indicates a read-only operation via 'Get'. It does not mention traversal order or error behavior, but the core behavior is transparent.

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?

A single sentence that states the action, scope, and output. It is front-loaded and contains no filler, making it highly efficient for an agent to parse.

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 adequately covers the tool's purpose and return content despite lacking annotations and an output schema. It does not detail the response structure or behavior for invalid paths, but the simplicity of the operation and schema documentation for maxDepth are sufficient for most use cases.

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 input schema already provides 100% coverage for both parameters, including the dot-notation format for 'path' and the meaning of 'maxDepth'. The description adds no parameter-specific details beyond restating 'path' context, so it does not improve on schema semantics.

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 the specific verb 'Get' with the resource 'descendants of an instance at the given path', and clarifies the output ('classNames and full paths'). This distinguishes it clearly from sibling tools like get_children, which returns only direct children.

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 phrase 'all descendants' implies traversal of the full instance hierarchy, suggesting when this tool is appropriate. However, it does not explicitly state when to prefer this over alternatives (e.g., get_children for direct children), so usage guidance remains only implied.

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