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

Beyond the annotations (readOnlyHint, openWorldHint, non-idempotent), it discloses what the call returns (top three with confidence, detected tonic, page links) and a privacy-relevant trait: "The recording is not stored." The URL must be public, which clarifies the open-world network requirement.

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?

Three short sentences, front-loaded with the action and input, then results, then practical guidance. Every clause carries information: format, size, output shape, and the no-storage guarantee.

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 one parameter, no output schema, and a simple read-only operation, the description covers input constraints, expected return contents, and best-case audio conditions. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the single parameter is documented as a public audio link, so the baseline is already met. The description adds real meaning the schema lacks: accepted formats (mp3, wav, m4a, ogg, webm) and the 25 MB cap, which directly govern whether the URL value will be accepted.

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 gives a specific verb ("Name the raaga") plus the exact resource (a recording of Carnatic or Hindustani music at a public URL). It implicitly distinguishes itself from siblings such as list_raagas and find_raaga, which operate on names or catalogs rather than audio, so an agent can route to 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?

It states clear conditions for good results ("Best with a minute or more and a drone") and the accepted input formats and size. It does not explicitly exclude cases or name a sibling alternative (e.g., for naming a raaga from text), so it falls short of a full when/when-not rubric.

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