confluence_get_page_ancestors

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

The description indicates a read-only operation, but lacks details on the exact list returned (e.g., all ancestors up to root, order), error behavior, or any requirements. Without annotations, the description carries the full burden and falls short.

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 a single sentence, which is concise. However, it lacks structure and does not include any additional context or usage hints that would make it more helpful. It is adequate but not exemplary.

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 simplicity of the tool (one required parameter, no output schema), the description is minimally complete. It does not explain the return format, pagination, or hierarchy traversal, leaving significant gaps for an agent.

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 coverage is 100% as the single parameter 'pageId' has a description. The tool description adds no additional meaning beyond what the schema already states. Baseline score of 3 applies.

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 'Get ancestor pages of a page' clearly conveys the tool's verb (get) and resource (ancestor pages). It is distinct from sibling tools like 'confluence_get_child_pages' due to the different direction of hierarchy. However, it could be more specific about what 'ancestor pages' entails.

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?

No guidance is provided on when to use this tool versus alternatives such as 'confluence_get_page' or 'confluence_get_child_pages'. The description does not mention any prerequisites or context for use.

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