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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value by listing the return payload (synopsis, links, related entries), but says nothing about the media_type requirement, rate limits, or behavior when slug vs title is ambiguous.

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?

A single dense sentence that front-loads the resource and the payload. The long comma list of return fields is slightly padded but every element is informative.

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 read-only detail tool with no output schema this is adequate but thin: it doesn't explain the media_type parameter's effect or behavior on lookup failure, leaving an agent to infer how to disambiguate anime vs manga.

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 50%; the slug/title dual-input meaning is echoed from the schema, and the optional media_type enum parameter is never mentioned in the description. Baseline 3 since the schema handles what little there is.

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?

States a specific verb ('Full details') and resource ('one anime, manga or webtoon') and enumerates exactly what is returned. It is clearly distinct from siblings like search_titles or resolve_title.

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 use after search by noting the slug 'from search results', but it never explicitly contrasts with siblings like resolve_title or search_titles, nor states when not to use it. Implied usage only.

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