export_epub

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that the tool can overwrite files (despite the confirmDestructive parameter), that it may include images by default, or that it supports multiple EPUB versions and image formats. The description is a bare statement of intent with no behavioral context, leaving the agent unaware of side effects like file overwriting or default behaviors.

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, efficient sentence with no wasted words. It front-loads the core action and format. However, it is so brief that it misses opportunities to add behavioral context, but for what it states, it is concise and well-structured.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the overwrite confirmation requirement, the default EPUB version, or the image handling behavior. An agent would need to inspect the schema carefully and still might not know when to choose this over export_pdf or export_images. The description is minimally viable but leaves significant gaps.

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 60%, so the schema already documents filePath, imageFormat, includeImages, and confirmDestructive. The description adds no parameter-level detail beyond what the schema provides. The version parameter lacks a description in the schema and the description doesn't compensate, but the enum values are self-explanatory. Baseline 3 is appropriate since the schema does most of the work.

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 'Export document as EPUB' clearly states the verb (export), resource (document), and target format (EPUB). It distinguishes from sibling tools like export_pdf and export_images by naming the specific format. However, it doesn't explicitly differentiate from other export tools or mention the document context (e.g., current open document), which would make it fully unambiguous.

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 provides no guidance on when to use this tool versus alternatives like export_pdf or export_images. It doesn't mention prerequisites (e.g., a document must be open), nor does it explain when EPUB export is appropriate. The only implied usage is 'export as EPUB,' which is not enough to route an agent correctly among the many sibling export tools.

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