Get Space Page Tree

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

Annotations already mark the tool as read-only (readOnlyHint: true). The description adds value by detailing the flat list output, parent_id and depth attributes, and token efficiency. It provides useful behavioral context beyond the annotations.

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 well-structured, with a concise intro, key attributes, usage context, and clearly labeled args/returns. Every sentence adds value without redundancy, and it is appropriately sized for the tool's complexity.

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 presence of annotations, a complete output schema, and only two parameters, the description covers all necessary aspects: purpose, usage guidance, behavioral details, and parameter hints. It is fully adequate for an AI agent to correctly invoke the tool.

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?

The input schema fully describes both parameters (space_key and limit) with 100% coverage. The description adds a minor usage hint ('start with 100 for faster results') but does not significantly enhance understanding beyond the schema.

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 it retrieves the page hierarchy for a Confluence space as a flat list, using specific verbs and resources. It distinguishes itself from siblings like 'get_page_children' by explaining the flat list structure and efficiency, making the purpose very clear.

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 advises using this tool 'to understand space organization before creating/moving pages' and suggests filtering by depth or finding pages by title. It implies the context but does not explicitly exclude alternative tools like get_page_children, though the distinct output makes usage clear.

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