confluence_children

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

The description adds the behavioral trait of optional recursion with max depth beyond what annotations (none provided) convey. However, it does not disclose other important behaviors like pagination, rate limits, or access requirements. Given no annotations, the description carries the burden but provides only partial coverage.

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 short and front-loaded with the core purpose. The second sentence adds recursion info. The reference to the CLI tool is slightly noisy but not excessive. Overall efficient.

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?

The description lacks information about output format, pagination, error handling, and access permissions. Without an output schema, the agent is left guessing about the return value. Given the tool has four parameters and no output schema, the description should provide more context.

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 the parameter descriptions in the schema are already comprehensive. The tool description does not add any new information about parameters beyond what is in the schema. Baseline score of 3 is appropriate.

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 tool lists children of a Confluence page or top-level pages in a space. It mentions recursion and distinguishes two modes (by page ID or space). However, it does not explicitly contrast with sibling tools like confluence_read or confluence_search.

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 provides no guidance on when to use this tool versus alternatives. The reference to a CLI mirror (`omni-dev atlassian confluence children`) is not useful for an AI agent. It does not specify prerequisites, when to avoid, or how to choose between id and space.

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