confluence_get_page_ancestors

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

No annotations provided, so description carries full burden. It discloses default trimming behavior and the option to receive raw response, and specifies the order of ancestors. This is comprehensive for a retrieval tool.

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?

Two sentences, no extraneous words. Core information is presented first: action, resource, and scope. Very 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?

No output schema, but description specifies what is returned (list of ancestors from immediate parent to root) and the trimming behavior. This is sufficient for an agent to understand the tool's outcome. Could be slightly improved by mentioning the output structure (e.g., array of page objects), but not necessary.

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%, so baseline is 3. Description adds value by explaining the effect of `full=true` and implying the ordering of results, which is not in the schema. This justifies a 4.

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 verb 'Get ancestors' and the resource 'parent pages', and specifies the scope: 'from immediate parent to root'. This distinguishes it from sibling tools like `confluence_get_page_descendants` and `confluence_get_page_children`.

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?

Explicitly states what the tool does and mentions a key parameter (`full=true`) for controlling output. While it doesn't explicitly state when not to use it, the purpose is clear enough that an agent can infer usage context relative to sibling tools.

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