view_confluence_page

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

No annotations provided, so description carries full burden. It only says 'gets content' without disclosing access requirements, rate limits, or what 'content' includes (body, children, attachments?). The output schema exists but is not referenced; behavior remains opaque.

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?

Single sentence is concise, but it sacrifices informativeness. Could front-load more details about required input or output type without adding significant length.

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 one parameter and an output schema, the description should explain what the output contains and how to interpret results. It fails to do so, making the tool incomplete for autonomous use.

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 single parameter page_id has 0% schema description coverage, and the tool description does not elaborate on its meaning or how to obtain a valid ID. This leaves the agent guessing, requiring external knowledge.

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 states 'gets the content of a Confluence page,' which clearly identifies the action (get) and resource (Confluence page content). It distinguishes from sibling tools like list_confluence_pages (which lists pages) or edit_confluence_page (which modifies). Lacks minor details like whether content includes metadata or attachments, but overall clear.

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?

No guidance on when to use this tool versus alternatives (e.g., search or list tools for finding a page first). An agent is not told that page_id must be obtained beforehand or that this tool is for viewing full content, not for searching.

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