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

Annotations already declare readOnly, idempotent, and closed-world, so safety behavior needs no restating. The description does add real substance beyond them by disclosing the result set size, its tradition split, and two returned fields (parent, page), though it says nothing about ordering, result shape, or pagination.

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?

A single compact clause with zero filler, and the most decision-relevant fact (the catalog scope) comes first. It is a noun phrase rather than a sentence, so the action depends on the title, a minor structural weakness.

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 low-complexity enumeration tool with one optional enum parameter and no output schema, the description covers scope, breakdown, and key returned fields. Only ordering and response format are left open, which is a small gap at this complexity level.

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 single optional 'tradition' filter is fully documented in the schema with an enum, so the baseline is 3. The description adds partial semantic value by stating the 40/30 Carnatic-Hindustani split, which tells the agent what filtering by tradition will actually select, even though it never names the parameter.

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 precisely (the 70 raagas, split 40 Carnatic / 30 Hindustani) and what each entry carries (parent and page), which is enough to tell it apart from find_raaga and identify_raaga. It relies on the title for the verb 'List', so the action itself is only implied by the description text.

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 explicit when-to-use statement and no routing to siblings such as find_raaga for targeted lookup. The enumeration framing implies browsing the full catalog, but the agent must infer that this is the choice when it needs an overview rather than a specific raaga.

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