export_confluence_page

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

The description discloses a genuinely useful behavioral trait beyond the schema: images are embedded as base64, making the output self-contained, which has real consequences for file size and portability. Since no annotations are provided, the description carries the full behavioral burden, yet it omits the return format (file path, data, or download URL) and any page-size or performance limitations.

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?

Three sentences, each earning its place: the core purpose, the key behavioral detail about base64 image embedding, and the usage guidance. The primary action is front-loaded in the first sentence with no filler, redundancy, or restatement of the tool name.

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?

The tool is simple (2 required parameters, full schema coverage, no nested objects) and the description covers purpose, behavior, and usage. However, since there is no output schema, the description should state what the agent receives after the export (file location, data blob, or download URL), which is a meaningful gap for a tool that produces a deliverable file.

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%, with both pageId and format already documented, so the baseline is 3. The description adds only marginal reinforcement by tying the format parameter to a behavioral outcome (both formats embed images) without providing deeper parameter-level detail.

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?

States a specific verb ('Exports'), resource ('Confluence page'), and scope (HTML or Markdown with embedded images), which fully defines the operation. This clearly distinguishes it from siblings like read_confluence_page (which reads content) and download_confluence_attachment (which downloads individual attachments), so an agent can select it without ambiguity.

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 bolded instruction 'Use this when you want to create a portable, self-contained file of a page' provides explicit when-to-use guidance that is easy to match against an agent's goal. However, it does not name alternatives or state when-not-to-use it, so it stops short of the fully explicit exclusionary guidance.

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