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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false). The description's only behavioral addition is cross-chapter continuation, and it references a 'next' navigation concept that has no corresponding schema parameter, which is more confusing than clarifying. No return-format or pagination mechanics are disclosed.

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 opening 'Scroll the Lore' is not the tool's function, and the sentence sprawling across 'daily readings ... plans, search, and the whole Theogony, Iliad, Odyssey and Poetic Edda' spends most of its length on feature lists tied to siblings rather than this tool's job. It is neither front-loaded nor free of wasted content.

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 read-only, fully-documented-schema book reader with annotations covering safety, the definition is minimally viable: a caller learns the domain and the reading model but not how to disambiguate from the other lore reading/search tools. Given no output schema, some explanation of the sequential return behavior would help.

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 100%, so the schema already documents book, section, n, and ref in detail (including examples and override semantics). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 name and title hint at sequential passage reading, and the description says the corpus is 'read a passage at a time.' However, the lead 'Scroll the Lore' is vague and the body conflates features that belong to sibling tools ('daily readings explained line by line, plans, search'), muddying what this one tool actually does relative to lore_get_reading, lore_get_today, and lore_search_readings.

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?

It implies sequential progress ('Follow next for the next passage; it carries on into the next chapter') but never states when to pick this tool over lore_get_reading, lore_get_today, or lore_search_readings. No exclusions or precondition guidance are given.

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