wiki_list_children

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

No annotations provided, and description only states '列出所有直接子文档' without disclosing behavioral traits like pagination, recursion depth, or authentication requirements. Minimal transparency.

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?

Description is a single efficient sentence with no wasted words, but lacks structure such as parameter explanations or return format.

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?

Despite simple tool and existing output schema, description omits what the output contains or any limitations. Adequate but could be more complete.

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 0% and the description adds no meaning to the single parameter 'parent_id'. The agent gets no additional info beyond its type and requirement.

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?

Description clearly states the tool lists all direct child documents of a specified parent document, using specific verb-resource '列出所有直接子文档'. This distinguishes it from sibling tools like wiki_get_document (single document) and wiki_get_document_tree (hierarchical).

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?

Description implies usage for retrieving children of a parent, but lacks explicit when-to-use or when-not-to-use guidance, and does not mention alternatives among siblings.

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