list_document_children

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds useful behavioral context: pagination via next_offset/previous_page, metadata-only returns, and non-recursive scope. It doesn't detail errors or rate limits, so a 3 is appropriate.

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 compact sentences, front-loaded with the core action and selection method, followed by scope exclusions and pagination. No filler.

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?

An output schema exists, so return values needn't be explained, and annotations carry safety. The description covers scope, selection, and pagination. The main gap is incomplete coverage of several non-obvious parameters (detail, section_offsets, text_offsets) given the low schema coverage.

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 only 38%, so much of the param meaning rests on schema field names alone. The description mentions url, parent_entity_uid, and pagination (next_offset/previous_page) but never explains limit, detail enum, offset, section_offsets, or text_offsets. It adds some value but does not compensate for the coverage gap.

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?

States a specific verb (List), resource (immediate children of a Kaiten document/group), selection method (URL or parent_entity_uid), and explicitly scopes to 'one page' and 'immediate children'. It clearly distinguishes itself from siblings like get_document or search_cards.

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?

Explains the two selection mechanisms and states the exclusions ('no recursive traversal or content download'), plus pagination follow-up with next_offset/previous_page. No explicit alternative-tool routing, but context is clear and the boundary is well-drawn.

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