anime_character_search

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

With no annotations, the description discloses pagination, returned fields (name, native name, image, favourites), and credential-free access. It doesn't mention rate limits or other constraints, but the provided information is sufficient.

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?

Two sentences: the first states the core purpose, the second adds details on results and pagination. No wasted words, well-structured.

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 no output schema, the description explains the return format (summaries with specific fields) and pagination. The tool is simple and the description covers all necessary context for an agent to use it correctly.

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?

All three parameters (page, query, per_page) are already described in the input schema with 100% coverage. The description adds 'paginated' and 'by name' but does not provide additional parameter-level meaning 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 searches anime & manga characters by name, returning paginated summaries. It distinguishes from siblings like anime_search (which searches titles) and anime_character (likely single character details).

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 for character name searches but does not explicitly state when not to use or provide alternatives. No guidance on excluding other search scenarios.

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