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

The description adds valuable context about the output structure, specifying that each genre listing includes both the number of artist profiles and a direct link to the genre page. This goes beyond the safety assurances provided by the annotations.

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 highly concise and efficient. It combines the key information—resource, content, and additional metadata—into a single, front-loaded summary.

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?

Given that the tool is parameter-less and includes an output schema, the description provides all necessary context for the AI agent. It fully describes the nature of the data it will receive.

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?

With zero parameters, the description must compensate for missing semantic information. The description fulfills this requirement by detailing the content of the returned list, which would otherwise be opaque without the output 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 purpose is extremely clear: it lists the genres available in the specific catalogue (TopAIMuza.pl). By providing examples like 'disco polo, rap, pop, rock', it immediately sets the expected resource type.

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?

Since this tool takes no parameters and serves as a foundational list, its usage is inherently clear for discovery. While it doesn't explicitly state 'use this over X', its purpose as a high-level catalog view makes its intended use obvious.

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