get_children

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

Discloses that the operation is read-only and does not recompute semantic classification. Since no annotations are provided, the description carries the full burden and covers key behavioral traits, though it omits error handling details.

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?

Three sentences that front-load the core action, then return type, then usage guidance. Every sentence adds value with 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?

For a simple tool with one parameter and no annotations, the description covers purpose, behavior, and alternatives. It lacks explanation of return format, but that is reasonable 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?

Schema description coverage is 100% for the single parameter, and the description ('Relative path from OBSIDIAN_ROOT') adds no new meaning beyond the schema schema definition.

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 clearly states the action ('Traverse the hierarchy downward'), the resource ('one note'), and the output ('all direct and transitive child note paths'). It also distinguishes from sibling tool 'get_parents' by mentioning the opposite direction.

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 with a concrete question ('what does this topic/module contain?') and names the alternative tool ('Use get_parents for the opposite direction').

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