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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description does add one useful behavioral trait: sequential pagination ('follow next... it carries on into the next chapter'), implying the reader advances continuously. It offers nothing about return format, error behavior, or permissions, which is a modest gap given the annotations already carry safety.

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 opens by restating the title almost verbatim ('Stoic Scroller. Follow next for the next passage; it carries on into the next chapter'), which is wasted space before any new information. It then bundles in unrelated-sounding mentions of 'plans, search', diluting the focus of an otherwise short passage-reading tool.

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 tool with full annotation coverage, complete parameter schema, and no output schema, the description needn't explain returns. But it fails to clarify its relationship to the crowded stoics_* family, and the 'next passage' continuity claim is not tied to any parameter or output, leaving an agent uncertain how it differs from get_reading.

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 fully documents n, ref, book, and section, including ref-overrides-section behavior and Bekhorot/Daf Yomi defaults. The description adds no parameter-level detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 names the corpus (Marcus Aurelius, Epictetus, Seneca; Meditations, Enchiridion, letters) and the mechanism ('read a passage at a time'), which conveys the general resource. However, the operation is blurred by side references to 'plans' and 'search' that are likely handled by sibling tools, and it never cleanly distinguishes this from stoics_get_reading or stoics_get_today. The purpose is inferable but not crisply stated.

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?

There is no explicit guidance on when to use this tool versus its many siblings (stoics_get_reading, stoics_get_today, stoics_search_readings, stoics_list_books). The mention of 'search' and 'plans' hints at other capabilities but never routes the agent to an alternative tool. Usage must be inferred entirely from the name.

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