confluence_get_page

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

No annotations are present, so the description carries the behavioral burden. It clearly indicates a read-only 'Get' operation and enumerates the returned fields (title, spaceKey, markdown body, version number, last-modified date), giving the agent a solid expectation of the result.

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, focused sentence that front-loads the core action and then lists the return payload. Every phrase earns its place, with no redundant filler.

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 simple one-parameter page retrieval tool, the description is complete: it explains what is fetched, how to identify the page, what fields are returned, and how page IDs can be found. No output schema exists, but the return fields are explicitly enumerated.

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%, and the pageId parameter is already well documented with a type, example value, and a pointer to confluence_search. The tool description adds only the 'numeric' detail, so it does not significantly go beyond what the schema already provides.

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 action ('Get'), the target resource ('full content of a Confluence page'), and the accessor ('by its numeric page ID'). It distinguishes itself from sibling tools like confluence_search and confluence_create_page by focusing on retrieving existing page content rather than searching or mutating pages.

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 implies this tool is appropriate when the caller already has a numeric page ID, and the schema explicitly routes ID discovery to confluence_search. It provides clear contextual guidance, though it does not explicitly state when not to use the tool.

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