get_kb_page

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

No annotations are provided, so the description carries full burden. It discloses what is returned (title, space, content, version, metadata) but does not explicitly state that the operation is read-only or discuss rate limits or authentication requirements. The word 'Get' implies no side effects, but more explicit disclosure would be beneficial.

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 extremely concise with two short sentences. It front-loads the primary action and returns values, with no redundant or extraneous information. Every sentence 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?

Given no output schema, the description lists key return fields. It covers the essential behavior for a simple retrieval tool. A minor gap is not specifying that pageId and url are mutually exclusive or handling of missing parameters, but overall it is fairly complete.

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. The description adds value by explaining that pageId and url are alternative identifiers and that content is returned as plain text. It also implies the use of includeRawContent by mentioning 'as plain text' contrast, though not explicitly. This adds semantic clarity beyond the schema.

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 'Get a Confluence/KB page by page ID or full URL', specifying both the resource and how to identify it. It distinguishes from sibling tools like get_kb_page_children and get_kb_page_comments by focusing on the page itself, but does not explicitly contrast with search_kb_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 lacks guidance on when to use this tool versus alternatives like search_kb_pages or get_kb_page_children. It implies that you need a known page ID or URL, but does not state prerequisites or provide selection criteria.

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