confluence_get_page

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

With no annotations, the description carries the full burden. 'Get' implies a read-only operation, which is transparent. However, it does not disclose error behavior, return format, or precedence rules when multiple parameters are provided. This is minimal but adequate for a simple read 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?

The entire description is one concise sentence that states the purpose and the two modes of lookup without any filler. Every word earns its place.

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?

For a get-by-identifier tool, the description is reasonably complete, but the combination of three optional parameters with no required fields and no output schema creates ambiguity about precedence and combined usage. The description does not address these edge cases, leaving minor but important gaps.

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 0%, so the description must compensate. It adds meaning by indicating that 'spaceKey + title' are paired together as an alternative to 'pageId'. However, it fails to clarify whether parameters are mutually exclusive, what happens if both are given, or whether spaceKey alone is valid. Some semantics added, but incomplete.

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 verb 'Get' and the resource 'Confluence page', and specifies two lookup methods: by ID or by spaceKey + title. This distinguishes it sharply from siblings like search, create, update, and comment, which have different actions.

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 clear context: use this tool when you have a page ID or a spaceKey/title pair. It does not explicitly mention alternatives or when not to use it (e.g., use search when you lack identifiers), but the context is sufficiently clear. Missing explicit exclusions prevents a 5.

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