children_list_children

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

With no annotations, the description carries the behavioral disclosure burden. 'List child profiles' clearly indicates a read-only operation, and 'get child IDs and slugs needed by other tools' explains the output's purpose. It omits possible pagination or result-size caveats, but nothing suggests destructive or unexpected behavior.

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 two short sentences with no filler. It front-loads the core purpose and immediately adds the most important usage instruction. Every sentence earns its place.

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 simple list operation, the schema covers parameters, and an output schema exists, the description is nearly complete. The workflow hint about calling this first adds valuable context. It could mention result-size behavior or pagination, but that is not critical for this tool's apparent simplicity.

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 all four optional parameters are already documented in the schema. The description adds no additional parameter-level meaning beyond the workflow context of returning IDs and slugs. Baseline of 3 is appropriate because the schema does the heavy lifting.

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 verb and resource: 'List child profiles.' It also communicates its role as the entry point for obtaining child IDs and slugs. However, it does not explicitly differentiate from siblings like children_get_child or children_create_child, so it lacks explicit sibling distinction.

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 instruction 'Always call this first to get child IDs and slugs needed by other tools' provides explicit when-to-use guidance and establishes the tool as a prerequisite. It does not mention when not to use it or name alternative tools, but the precedence guidance is strong.

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