Get genres

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

readOnlyHint=true already declares this is a safe read, so the description's burden is lower. It adds the useful downstream hint that returned slugs are the filtering keys, but says nothing about ordering, size, or return shape beyond slugs.

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 tight sentence with the core action front-loaded and the usage hint in parentheses. No wasted words, though it could surface the anime toggle.

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 one-optional-param read-only lookup with a fully documented schema and clear annotations, the description covers intent and output key (slugs) adequately. Only minor gaps like anime scope and ordering remain.

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 description coverage is 100%, so the 'anime' boolean and its default are fully documented in the schema. The description adds no parameter detail of its own, making baseline 3 correct.

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?

States a specific verb+resource ('List available genres') and no sibling overlaps with genre retrieval, so the agent can identify it easily among the many media tools. It stops short of clarifying the anime scope, which is the one dimension a sibling could be confused on.

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 parenthetical 'use the slugs to filter catalogs and lists' implies downstream usage but gives no explicit when-to-call guidance or prerequisites. Usage is inferable rather than stated, which fits the 3 tier.

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