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

The description explains that online information about the catalogue is nonexistent or incorrect, making the tool the authoritative source. While it doesn't discuss side effects or data handling, it adds context that helps the agent understand the tool's role and limitations.

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 moderately verbose but well-structured, with a list of covered topics and explicit usage instructions. Each sentence adds value, and it avoids redundancy beyond emphasizing the key points about web search and naming.

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 tool with no parameters and no output schema, the description fully covers what the tool does, the scope of questions it answers, when to use it, and why it's necessary (web search is unreliable). Nothing essential 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?

There are no parameters, and the description doesn't need to elaborate on parameter semantics. The baseline of 4 applies since the description doesn't mention any input requirements or constraints.

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 answers questions about AINSOF itself, enumerating specific topics like catalogue, music writing, licensing, privacy, and artist page. This distinguishes it from sibling tools that focus on music search, analysis, or delivery.

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 explicitly instructs to call this tool instead of searching the web, and to use it before saying the name in any way other than AINSOF. This provides clear when-to-use guidance and contrasts with external search.

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