export_book

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and resource but provides no insight into side effects (e.g., file replacement, path existence), permissions required, whether the book must be open, or any impact on the book state. The description is minimal and insufficient for a mutation tool.

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 sentence of 6 words, highly concise and to the point. It is front-loaded with the key action. While efficient, it lacks structure and could benefit from slightly more detail without being verbose.

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 the tool has 3 parameters, no output schema, and no annotations, the description is incomplete. It does not clarify the export process (e.g., output behavior, any prerequisites like the book being open), and the sibling tools like export_pdf suggest potential confusion. More context is needed for an agent to use this tool effectively.

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 clear descriptions for each parameter. The description adds no additional context beyond 'various formats' which is already implied by the enum. With high schema coverage, the baseline is 3, and no extra value is provided.

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 the verb 'Export' and the resource 'entire book', and mentions 'various formats' which gives a general sense of capability. However, it does not explicitly list the available formats (PDF, EPUB, HTML) nor differentiate from sibling tools like export_pdf or export_epub that target specific formats.

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 is provided on when to use this tool versus alternatives. For example, siblings like export_pdf and export_epub offer format-specific exports, but the description fails to clarify that this tool handles the entire book or that it might be the preferred choice for multi-format exports. There is no when-not or prerequisite information.

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