list_descendants

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

No annotations are provided, so the description must fully convey behavioral traits. It discloses the generations limit but does not clarify whether the individual is included, how results are ordered, or error handling. This lack of key behavioral context is a significant gap for a tool without annotation support.

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 a single, front-loaded sentence that conveys the core purpose and key limitation with no wasted words. The backticked 'generations' clearly references the parameter.

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?

For a simple read-only tool with an output schema, the description adequately states the purpose and depth parameter. However, it lacks usage guidance and behavioral details like self-inclusion or traversal order, making it only minimally complete for the given complexity.

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 schema has zero description coverage, so the description must compensate. It does so by mapping 'given individual' to individual_id and 'up to generations levels' to the generations parameter, giving each parameter a clear semantic. While not exhaustive (e.g., no mention of defaults), it covers the essential meaning.

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 'list' (from the tool name) with the resource 'descendants' and clearly scopes it to a given individual and a depth limit. This distinguishes it from siblings like list_children and list_ancestors by focusing on the descendant hierarchy.

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 implies usage for retrieving descendants up to a certain number of generations, but it does not explicitly compare with alternatives like list_children or list_ancestors, nor state when to use this tool over them. The depth limit hints at its broader scope, but guidance is not explicit.

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