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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not say what a 'card' contains, whether n indexes lines or cards, or how much output is returned per call.

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 repeats the tool title verbatim (even duplicating the trailing period), and the second sentence describes the whole Gurbani product surface rather than this tool. Space is spent on redundancy and off-topic content instead of front-loading useful specifics.

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 and a non-obvious return shape ('one line at a time'), the description should explain what is returned and how many lines/cards a call yields, but it does not. The core concept of a 'card' is left undefined, which is a meaningful gap for an agent trying to use it correctly.

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 already documented in the schema, which sets the baseline of 3. The description adds no extra meaning about parameter interaction (e.g. how n relates to reading/date) beyond what the schema states.

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 title/description states a reasonably specific idea (today's reading, one line at a time, for voice), which implies a verb (fetch) and resource (a line/card of a reading). However, it never clarifies what a 'card' is relative to siblings like get_reading or get_today, so an agent cannot reliably distinguish it without opening the schema.

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 when-not-to-use guidance, and no mention of the sibling tools (get_reading, get_today, get_ang, get_shabad). The second sentence is a catalog-level blurb about the Gurbani domain rather than routing guidance for this tool.

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