confluence_get_page

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

No annotations are provided, so the description carries the full burden. It does disclose a key behavior: body is converted from storage format to plain text by default, and mentions the format parameter controls this. However, it does not discuss potential errors, auth requirements, or what other fields are returned, leaving some behavioral aspects undisclosed.

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 that immediately states the action and resource, then clarifies the body handling. Every word adds value, with no redundancy or 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?

Given the low complexity (2 params, 1 required) and no output schema, the description is sufficient to convey the core function and body format behavior. It could mention that other page fields are returned, but for a simple fetch-by-id tool this is not a critical omission. The absence of annotations is partially compensated by the explicit body conversion note.

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?

The input schema describes both parameters fully (pageId as numeric string, format enum with descriptions). The description's reference to 'storage format converted to plain text' aligns with the schema but does not add meaning beyond it. With 100% schema coverage, 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 the specific verb 'Fetch' with the resource 'Confluence page by id', and explicitly notes the body conversion behavior. It clearly distinguishes from sibling tools like confluence_search, confluence_create_page, and confluence_update_page, which have different verbs and purposes.

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 clearly indicates when to use the tool: to fetch a page by its id. It does not explicitly mention exclusions or alternatives, but the context of 'by id' implies this is for targeted retrieval rather than search or modification. The lack of explicit 'when not to use' is a minor gap.

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