export_confluence_page

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

Discloses that images are embedded as base64 data, making the file self-contained. However, it does not specify what the tool returns (e.g., file path, content blob), and no annotations exist to fill that gap.

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?

Two concise sentences plus a bolded usage statement. No wasted words, front-loaded with the core action.

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?

Covers core purpose, format options, and key behavioral trait (image embedding). Missing any description of the output's nature or handling, but adequate given the tool's simplicity and lack of output schema.

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% with descriptions for both parameters. The description does not add meaningful semantics beyond the schema; it merely restates that images are embedded.

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?

Clearly states the verb 'exports' and the resource 'Confluence page', specifies two formats (HTML or Markdown), and distinguishes from unrelated siblings by emphasizing the portable, self-contained file output.

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?

Explicitly says 'Use this when you want to create a portable, self-contained file of a page,' providing a clear when-to-use directive and implying it should not be used for simple reading.

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