Search E-Hentai galleries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description only needs to add behavioral nuance. It adds important context about native syntax and filter capabilities, which aids understanding without contradicting annotations.

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 concise at one sentence, front-loading the core action. It could benefit from a brief pause after the first clause, but it's efficient and free from redundancy.

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 high parameter count (14) and low schema coverage (29%), the description should compensate by explaining how filters relate to parameters. It mentions filters but not their exact parameter names (e.g., minRating, categories). The presence of an output schema reduces the need to describe return values, but the filter mapping gap persists.

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 only 29%, meaning most parameters have no schema description. The tool description lists filter categories (category, rating, page-count, torrent, expunged, cursor) but does not explain which parameter maps to which concept or add usage details for all 14 parameters. This leaves significant ambiguity for an AI agent.

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 E-Hentai or ExHentai using native tag/title syntax, and lists optional filters. It distinguishes it from sibling tools like eh_search_favorites by specifying broad gallery search, though it doesn't explicitly contrast with all siblings.

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 this is for searching galleries by query and filters, but does not specify when to use alternatives like eh_find_similar_galleries or eh_search_by_hash. No exclusion criteria or prerequisites are mentioned.

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