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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds one genuine behavioral trait, that output is delivered 'one line at a time, for voice,' which is useful but thin; it says nothing about determinism across dates or the shape of a card.

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 verbatim, down to the double period ('for voice..'), which is pure repetition. The second sentence is broad product marketing listing Theogony, Iliad, Odyssey, Edda, plans, and search, none of which helps invoke this specific tool, and the front-loaded content is the least informative part.

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 full schema coverage and rich annotations, the description only needs to clarify the tool's role and output concept, yet 'card' and 'line at a time' are never defined and the relationship to lore_get_today is unstated. It is minimally viable but leaves an ambiguity an agent must resolve.

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%, with n, date, and reading all fully documented in the schema itself, so the baseline is 3. The description adds no parameter detail beyond a vague mention of 'plans' and 'search,' leaving the schema to do all the work.

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 identifies the resource loosely as 'today's reading one line at a time' and hints the output is voice-oriented, but 'Scroll the Lore' and 'card' remain undefined, and it never distinguishes lore_get_card from close siblings like lore_get_today or lore_get_reading. An agent can guess it retrieves a daily reading fragment but cannot tell why it would pick this tool over its siblings.

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 phrase 'for voice' faintly implies a TTS/voice use case, but there is no explicit when-to-use, no when-not, and no named alternative among the six sibling lore_* tools. Guidance is essentially absent.

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