Search characters

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context: 'Returns compact summaries and the mal_id needed by get_character.' This clarifies the output format and its role as a prerequisite, going beyond schema and annotations. However, it doesn't detail pagination or sorting behavior beyond what the schema provides.

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. The first sentence states the primary purpose. The second sentence provides clear alternative usage guidance. No unnecessary words or complexity.

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 the tool has 6 parameters and an output schema (not provided but mentioned in context), the description is complete enough. It adds critical context about the output (compact summaries, mal_id) and links to related tools. It doesn't repeat schema details, which is appropriate.

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 description coverage is 100%, so all parameters are documented in the input schema. The description adds minimal extra meaning beyond the schema, only implicitly connecting the 'q' parameter to 'by name'. With full schema coverage, the baseline of 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 what the tool does: 'Search MyAnimeList characters by name.' It specifies a specific verb (Search) and resource (MyAnimeList characters), and distinguishes itself from the sibling tool get_anime_characters by noting it returns compact summaries and the mal_id needed for get_character.

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 provides explicit guidance on when to use this tool vs. an alternative: 'Use get_anime_characters instead if you already have an anime's mal_id and want its full cast.' This clearly defines the context for this tool (when you don't have an anime ID) and directs to the appropriate sibling.

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