Get manga statistics

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

The description aligns perfectly with annotations (readOnlyHint=true, openWorldHint=true). It explicitly states the tool is a 'get' operation and specifies the returned statistics (read-status counts, score distribution), adding behavioral context beyond the 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 concise sentences with no filler. It front-loads the primary purpose and efficiently provides necessary context about the id source.

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?

With one clear parameter and no output schema, the description sufficiently covers what the tool returns (read-status counts and score distribution). It doesn't detail exact structure, but for a statistics tool, the provided context is adequate.

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 input schema covers the only parameter 'id' with a description. The description adds value by explaining the parameter is the mal_id and where to obtain it (from search_manga), enhancing understanding beyond the schema.

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 retrieves 'read-status counts' and 'score distribution' for a manga by its mal_id. It also explicitly directs the agent to obtain the id from 'search_manga', distinguishing it from general manga retrieval tools like 'get_manga'.

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 instructs the agent to get the mal_id from 'search_manga', implying the tool is used after finding a manga. While it doesn't explicitly state when not to use it or list alternatives, the context of being a statistics tool is clear among sibling tools.

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