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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, yet the description still adds real behavior: the site does not paginate a genre, so the entire list comes back in one response. It also flags that authors appear only "when printed" and that a genre total is included, useful for anticipating partially-null fields. No cost/size warnings beyond "whole list" are given.

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?

Content is front-loaded and each sentence carries new information: field inventory, prerequisite, ordering, and pagination behavior. The opening sentence is a long comma-chained field list that is denser than necessary but still readable.

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 single-genre listing tool, everything an agent needs to call it correctly is present: where to get the slug, how to order results, and the absence of pagination. An output schema exists, so return-value documentation is not the description's burden, and the annotations cover the safety profile.

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%, so a 3 is the floor, and the description earns an extra point by identifying webtoon_genres as the authoritative source for valid genre slugs — context the schema cannot express since genre is a plain string with no enum. The sort options restate the schema's own list, adding little.

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?

"List every WEBTOON series in one genre in a single response" gives a specific verb, resource, and scope, and the description enumerates the returned fields (title_no, title, authors, thumbnail, URL, counter, UP badge, genre total). It also names webtoon_genres as the source of the genre slug, which separates it from the broader series/rankings siblings.

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 the prerequisite workflow (get the slug from webtoon_genres) and the ordering control (MANA, LIKEIT, UPDATE), which is clear usage context. It stops short of saying when to prefer webtoon_rankings or webtoon_search instead, so there are no explicit exclusions.

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