Get manga news

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

Annotations already declare readOnlyHint and openWorldHint, so description adds value by explaining the sfw/sfw_strict filters' non-trivial effect (verified live, can cut results sharply but not to zero) and the return fields. No contradiction with 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 four sentences, front-loaded with purpose, and every sentence adds value. There is no wasted text, and the structure efficiently conveys purpose, usage, and parameter behavior.

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 simplicity, the presence of an output schema, and clear annotations, the description covers all essential aspects: what it does, how to use it, when to choose alternatives, and key parameter nuances. It is fully adequate for an agent to select and invoke correctly.

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%, baseline 3. The description goes beyond schema by explaining that sfw alone allows Ecchi genre while sfw_strict excludes it, and that both are not no-ops. This adds meaningful context beyond the schema's descriptions.

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 tool lists recent news articles about a manga by mal_id, specifies the output fields (headline, date, author, excerpt), and distinguishes it from the sibling get_news tool for site-wide feed. The verb 'list' is specific and the resource is well-defined.

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 ('what's new / any announcements'), how to obtain the required mal_id (via search_manga), and when to use the alternative get_news for a site-wide feed. It also explains the sfw/sfw_strict filter behavior, providing clear usage guidance.

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