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 profile is covered. The description adds only 'one line at a time, for voice', which hints at output granularity and channel but says nothing about pagination, ordering, or what the card content is.

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 duplicates the title verbatim (including a stray double period), then appends a run-on sentence mixing unrelated app features. It is not front-loaded with tool-specific information and wastes its first clause on repetition.

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 0 required params, rich annotations, and full schema coverage, the structured data does most of the work, but the remaining ambiguity of what a 'card' returns and how it differs from get_today/get_reading is unresolved and no output schema compensates. The description leaves the agent unable to confidently pick this tool over its siblings.

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 'n', 'date', and 'reading' are fully documented in the schema with defaults and formats. The description adds no additional meaning about these parameters (e.g., how 'n' interacts with a reading), 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 first sentence is a near-verbatim restatement of the title ('Today's reading one line at a time, for voice..'), and the second is app-level marketing copy ('Bhagavad Gita: daily verses, plans, search and verse lookup; whole books from the Library') that describes the whole product rather than this tool. It never explains what a 'card' actually is, so the agent cannot clearly distinguish get_card from get_today, get_reading, or get_verse.

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 and no comparison against the many similarly-named siblings (get_today, get_reading, get_verse, get_chapter). The mention of 'search and verse lookup' hints at neighboring functionality but never states which tool to use for which need.

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