search_manga

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

No annotations are provided, so the description carries the full burden. It states it returns 'search metadata only', which implies a read-only operation, but doesn't disclose behavioral traits such as rate limits, authentication needs, pagination, or error handling. This is a significant gap for a search tool with no annotation coverage.

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 a single, efficient sentence with zero waste. It front-loads the key action and resource, making it easy to parse quickly without unnecessary elaboration.

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's moderate complexity (a search function with one parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete behavioral disclosure, it lacks depth for safe and effective use, though the output schema mitigates some gaps by defining return values.

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 schema description coverage is 100%, with the single parameter 'query' fully documented in the schema. The description adds minimal value by mentioning 'by title', which aligns with the schema's 'manga title to search for', but doesn't provide additional syntax, format details, or constraints beyond what the schema already covers.

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 action ('Search MangaDex by title') and the resource ('MangaDex search metadata'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get_manga_details' or 'get_manga_chapters', which might also involve manga data retrieval but with different scopes or purposes.

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 no guidance on when to use this tool versus alternatives. It mentions returning 'MangaDex search metadata only', which hints at the output type, but doesn't specify scenarios, prerequisites, or exclusions compared to siblings like 'get_manga_details' for detailed info or 'get_manga_chapters' for chapter lists.

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