epub_to_audiobook

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

With no annotations, the description covers behavioral traits: async polling, payment via Bitcoin Lightning, voice tier options with rates, and translation cost. It also specifies the need for a prior create_payment call. Minor omissions: no mention of error handling or failure modes beyond polling.

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 moderately concise, packing essential information into a few sentences. It front-loads the primary purpose and then elaborates on key details. Could be slightly tighter but remains efficient.

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 complexity and lack of output schema, the description provides sufficient context for an agent to understand the workflow: asynchronous execution, polling, payment integration, and voice tier trade-offs. It does not cover all edge cases but is adequate for correct invocation.

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%, so parameters are well-documented in the schema. The description adds value by explaining voice tiers and payment integration but does not provide substantial new semantics for individual parameters beyond the schema.

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 tool converts books (EPUB/PDF/TXT) into full audiobooks with features like chapter detection, multi-voice narration, and translation. It distinguishes itself from sibling tools like text_to_speech by offering a comprehensive conversion pipeline.

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 implies usage for creating audiobooks from text files and mentions payment requirements, but it does not explicitly state when to use this tool versus alternatives (e.g., text_to_speech) or provide constraints (e.g., file size limits).

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