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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and idempotency profile is covered by structured data. The description adds the genuinely useful behavioral trait that output is chunked one line at a time for voice playback, but says nothing about termination (when there are no more cards) or how n relates to total length.

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 distinctive behavior ('one line at a time, for voice') is front-loaded, which is good, but the sentence carries a doubled period typo and then appends generic server-level Bible boilerplate that does not help invoke this specific tool. Roughly half the text is not earning its place.

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 no output schema, the description carries the burden of explaining the return shape for a paginated-by-line tool. It implies iteration via n but never explains how an agent knows it has reached the end, how many lines a reading contains, or what a single 'card' contains — key gaps for correct calling.

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 n ('which card, starting at 1'), date (YYYY-MM-DD, defaults to today UTC), and reading (a plan/reading id). The description adds no syntax, format, or range detail beyond the schema, so the baseline of 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 a specific behavior — today's reading delivered 'one line at a time, for voice' — which is more than the opaque name 'get_card' suggests. However, it never defines what a 'card' is, and it gives no differentiation from close siblings like get_reading or get_today. The appended 'Bible: daily readings, plans, search and passage lookup' is server-level boilerplate, not tool-specific purpose.

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 when-to-use guidance, no statement of when to prefer this over get_reading, get_today, get_passage, or list_readings, and no prerequisites. The 'for voice' phrasing weakly implies a TTS/chunked-consumption context but never states the condition explicitly.

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