Get character details

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

Annotations (readOnlyHint, openWorldHint) indicate safety and dynamic data. The description goes beyond by detailing the sfw/sfw_strict parameters' effect on appearance lists, noting the live filtering behavior and the distinction between sfw (allows Ecchi) and sfw_strict (excludes Ecchi). No contradictions.

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 front-loaded with the primary purpose, then efficiently covers parameter details in two additional sentences. Every sentence earns its place—no redundancy or filler.

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 an output schema present, the description need not detail return values. It covers purpose, ID source, and parameter behavior thoroughly. For a straightforward lookup tool, this is complete and leaves no gaps.

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 covers all parameters (100%), giving baseline 3. The description adds crucial context: sfw/sfw_strict filter the character's appearance lists, not the character itself. This additional explanation aids correct parameter 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 full details for one character by mal_id, including bio, appearances, and voice actors. It also tells how to obtain the mal_id, distinguishing it from search_characters (which lists characters) and get_anime_characters (which lists characters for an anime). The verb 'Get' and resource 'character' are specific, making purpose unmistakable.

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 instructs to obtain the mal_id from search_characters or get_anime_characters, providing clear guidance on prerequisite actions. It does not explicitly state when not to use, but for a simple lookup tool, this is sufficient and avoids confusion with siblings.

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