get_book_outline

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

Discloses behavior for auto-split sections (synthesized title) and confirms no section text is returned. With no annotations, the description adequately covers behavioral traits, though it omits explicit read-only indication.

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?

Well-structured with purpose first, then details, then usage flow. However, the paragraph about auto-split sections is slightly verbose for the core purpose.

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 one parameter and no output schema, the description covers all necessary context: what it returns, what it doesn't, and how it fits into the typical workflow alongside sibling tools.

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?

The single parameter book_id is not described in schema (0% coverage). The description mentions it in the flow but does not explain what it is or how to obtain it, adding minimal meaning beyond the name.

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 it returns the chapter/section outline (the map for get_section). Distinguishes from get_section by specifying it returns metadata like chapter_index, title, page_start, and section details, not the text.

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 provides typical flow: list_books -> get_book_outline -> get_section. Also advises using search_book when the target section is unknown, offering clear when-to-use and when-not-to-use.

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