get_manga_ranking

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

No annotations are provided, so the description must disclose behavior. It only mentions the query parameter, without stating whether the operation is read-only, how results are ordered, what the response shape is, or any side effects. For a ranking endpoint, critical behavioral context is missing.

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 a single, focused sentence that immediately conveys the tool's core purpose. It is front-loaded and contains no filler or redundant phrasing.

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's moderate complexity (3 params, no annotations, no output schema), the description is incomplete. It does not mention pagination behavior, default ranking order, or the meaning of ranking types, leaving the agent without enough context to set expectations or handle results.

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 schema covers limit and offset with descriptions, but ranking_type is an enum without explanation. The description mentions 'ranking_type' but does not elaborate on its values or how it affects results. Since schema coverage is 67%, the description partially compensates but still leaves ranking_type semantics unclear.

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 action ('Fetch') and the resource ('manga rankings'), which is specific and distinguishes it from sibling tools like get_anime_ranking or get_manga_list. The name and description align without needing further clarification.

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 implies usage for fetching ranking data, but it does not explicitly contrast with alternatives like get_manga_list or explain when not to use it. There is no mention of prerequisites or exclusions, landing at the 'implied usage' level.

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