anime_character

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

No annotations are provided, so the description must fully cover behavioral traits. It states the tool returns a normalized character profile (read operation) and that it's credential-free public data, indicating no authentication or destructive actions. This is sufficient for a simple lookup tool.

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 sentences with no wasted words. The first sentence states the purpose and output fields, the second adds credential information. Every sentence adds value.

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 a single parameter, no output schema, and a clear list of return fields, the description is fairly complete. It lacks details on error handling or rate limits, but for a simple get-by-ID tool, it adequately informs 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?

The input schema has one parameter 'id' with description 'AniList character id' and 100% schema coverage. The description adds that it's an AniList ID and that the tool gets a character, but does not provide additional format details or constraints 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 'Get an anime/manga character' and lists the specific fields returned (names, image, description, etc.). It distinguishes itself from sibling tools like 'anime_character_search' which is for searching, while this tool retrieves a specific character by ID.

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 specifies the required input ('by AniList id') and notes that it's credential-free public data. It implies usage when you have an AniList ID, but does not explicitly mention when not to use it or suggest alternatives like search for query-by-name.

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