Get top manga

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and completeness. The description adds that the tool returns 'top' or ranked manga and mentions filter for special rankings, but does not detail pagination or output structure. Minimal added value beyond 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 two short sentences, both directly relevant. The first sentence states the core purpose, and the second provides actionable guidance on the filter parameter. No wasted words; all content earns its place.

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 tool with no output schema, the description does not explain the return format (e.g., list of manga with ranking info, ordering, or structure). It relies on the tool name and sibling context. While the schema and annotations cover safety and parameters, the lack of output description leaves a gap for the agent.

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% with clear descriptions for all 4 parameters. The description only highlights the 'filter' parameter, which is already explained in the schema. No new semantics added, so baseline 3 is appropriate.

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 'Get ranked/top manga', specifying the verb and resource. It distinguishes from sibling tools like get_top_anime (different resource) and search_manga (search vs. ranking) by its unique focus on top/ranked lists. The mention of filter parameter further clarifies specialization.

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?

No explicit guidance on when to use this tool versus alternatives like search_manga or get_manga. The description only hints at using 'filter' for special rankings, but does not explain when to choose this tool over siblings. The agent must infer from the tool name alone.

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