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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds only the special case that chapter 0 returns the chapter list, which is more parameter guidance than behavioral disclosure; no rate limits, output shape, or side effects are discussed.

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?

One compact sentence front-loads the trigger and includes the special 0 argument; every clause is useful and there is no filler.

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 simple one-parameter read-only tool with full schema coverage and strong annotations, the description supplies the purpose, trigger, and the special 0-case needed to call it correctly. No output schema exists, but the expected result ('summary'/'overview') is sufficiently implied.

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% and the single parameter's description already states '1-18, or 0 for all chapter names.' The description's '(pass chapter 0 for the list of all chapters)' reinforces this but does not add syntax, format, or meaning beyond the schema.

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 (Bhagavad Gita chapters) and the operation (summary/overview), and its chapter-level scope distinguishes it from verse-level siblings like get_gita_verse and search_gita. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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?

It states exactly when to use the tool—when the user asks what a chapter is about or wants an overview of all 18 chapters—and tells the agent to pass 0 for the chapter list. It gives no exclusions or alternative tools, so 4 rather than 5.

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