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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: reading is chunked ('a passage at a time') and continuation flows across chapter boundaries via 'next'. It does not describe error behavior or what a passage object contains, but the annotations carry most of the burden.

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 restates the tool name ('Talmud Scroller') and then repeats the title almost verbatim before appending a grab-bag clause about daily readings, plans and search that does not belong to this tool. Little is front-loaded as a purpose statement; the trailing feature list is noise that dilutes the signal.

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?

With 100% schema coverage, no output schema, and annotations covering the safety profile, the mechanics an agent needs to call the tool are present elsewhere. The description stops short of the one thing that would help most, routing between this and talmud_get_reading / talmud_get_talmud_text, and its suite-level marketing line muddies rather than completes the picture.

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%: book, section, n and ref are all documented in the schema, including the ref-overrides-section-and-n precedence and daf notation. The description adds no parameter meaning beyond this ('read a passage at a time' is already covered by the n field description), 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 description conveys that this reads a 'whole book' 'a passage at a time' and lets you 'follow next', so the read-a-book-sequentially purpose is inferable. However, it opens by restating the title and then drifts into a suite-level feature list ('daily readings, plans, search and original text lookup') that describes the whole Talmud toolset rather than this tool, and it never distinguishes itself from siblings like talmud_get_reading or talmud_get_talmud_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?

'Follow next for the next passage; it carries on into the next chapter' gives actionable navigation guidance for continuing a read. But there is no explicit when-to-use versus alternatives, no statement of when to prefer this over talmud_get_reading, and no prerequisites. Usage is only implied.

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