get_shabad_by_line

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

With no annotations, the description carries the burden. It discloses that it returns all lines in order, with Gurmukhi, transliteration, translation, and Ang reference, which is the key behavioral output. It also implies it is a read-only operation by using 'return', and provides workflow context. It does not cover edge cases or errors, but for a simple read tool this is adequate.

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 is two sentences, front-loaded with the core action and return details, and ends with a clear usage directive. Every word earns its place; no redundancy or fluff.

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?

For a single-parameter, no-output-schema tool, the description covers all necessary context: input (line ID), action (return full Shabad), output structure (all lines, fields), and usage scenario (after search_gurbani). It is complete for an agent to select and invoke 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?

The schema already provides 100% coverage, describing line_id as 'Any BaniDB verse ID from the Shabad you want'. The tool description's 'Given any line ID from the SGGS' adds no new meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states the tool 'return the complete Shabad (hymn)' given a line ID, listing the output fields. It distinguishes itself from siblings by specifying it expands a single line into the full hymn, explicitly pointing to search_gurbani as the preceding step. This is a specific verb+resource+scope.

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 description explicitly says 'Use this after search_gurbani', giving a clear when-to-use context. It does not mention when-not-to-use or alternatives, but the workflow guidance is unambiguous enough for this lookup tool.

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