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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description contributes one genuinely extra behavioral fact: output is delivered 'one line at a time, for voice', implying chunked/TTS-oriented returns. It still omits what a card contains and how pagination/indexing behaves, so it is only a partial addition.

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 first sentence duplicates the title including its typo ('for voice..'), and the second is a run-on list of domain content (search, plans, four epic works) that is mostly irrelevant to calling this single tool. Not front-loaded on the actual function, and the wasted duplication should be cut.

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?

There is no output schema, so the description carries the burden of explaining what a card is and what the call returns. It never does: 'card' is undefined, and it is unclear whether the tool returns a single indexed line, a whole passage, or the day's reading. For a tool with an opaque noun in its name, this is incomplete.

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% and all three parameters (n, date, reading) are fully documented in the schema, so the baseline of 3 applies. The description adds nothing about parameter behavior beyond the vague phrase 'one line at a time', which only loosely aligns with the schema's 'Which card, starting at 1'.

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 opens by restating the title nearly verbatim ('Scroll the Lore. Today's reading one line at a time, for voice..'), then pivots to marketing the whole mythology domain (Theogony, Iliad, Odyssey, Poetic Edda, plans, search). It never defines what a 'card' is or how this differs from its direct siblings lore_get_reading and lore_get_today, so an agent cannot tell what resource it actually fetches.

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 only usage cue is the fragment 'for voice', which implies a TTS/voice-assistant context, but no when-to-use or when-not-to-use is stated and no alternative sibling is named. Given six sibling lore_* tools including get_reading and get_today, the absence of routing guidance is a real gap.

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