get_page

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

No annotations are provided, so the description must carry the full burden. 'Get Confluence page content' only states the basic read operation and implies nothing about the return format, the effect of include_body, or any other behavioral nuances. It adds no transparency beyond the tool's name.

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 with zero fluff, which is very concise. However, its brevity borders on under-specification, sacrificing useful detail. It is well-structured and front-loaded, but lacks the informative value that would earn a 5.

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 there is no output schema and no annotations, the description is not complete enough. It doesn't explain what the response contains, how include_body changes the result, or what edge cases exist. The presence of sibling tools for related operations makes the lack of usage context more noticeable.

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%: both page_id and include_body have meaningful descriptions. The tool description itself adds no parameter-level meaning, but the schema already documents the parameters, so a baseline 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 uses a specific verb+resource ('Get Confluence page content') that clearly identifies the tool. It distinguishes from siblings like get_page_children and get_attachments, though it doesn't explicitly state what 'content' excludes. It is clear but not as rich as a fully differentiating description.

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. There is no mention of using it for full page retrieval, nor any indication of when to prefer search or get_page_children. The agent receives no context about which scenario this tool addresses.

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