Get genres

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds limited behavioral transparency beyond confirming it lists genre names. It provides context about the data source (AniList) but doesn't disclose additional traits like return format or pagination. The description does not contradict 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 extremely concise at two sentences, with the main purpose stated upfront. Every sentence adds value: the first defines the tool's output, and the second explains its practical use case. No wasted words.

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 the tool has no parameters and an output schema exists, the description is fully adequate. It explains what the tool returns (genre names), why it's useful (to feed into search_media filtering), and references the relevant sibling tool. This covers all necessary context for an agent to correctly invoke it.

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 tool has zero parameters, so the description need not explain parameter semantics. The baseline for zero parameters is 4, and the description appropriately focuses on the output and usage rather than parameters.

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 that the tool lists every genre name AniList uses to tag anime/manga, with examples like Action, Comedy, Slice of Life. It distinguishes itself from other tools by specifying its purpose in the context of filtering search_media by genre, making the purpose very clear and specific.

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?

The description explicitly tells when to use the tool: call it before filtering search_media by genre, to ensure you pass a recognized genre name. While it doesn't explicitly state when not to use it or mention alternatives, the guidance is clear and actionable for its intended use case.

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