Get E-Hentai search capabilities

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

Annotations already mark it as read-only, idempotent, non-destructive, and open-world. The description adds the critical behavior that it requires no network request, which aligns perfectly with the annotations and provides additional clarity. No contradiction.

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?

A single, front-loaded sentence conveys the full purpose and the key usage note (no network request). No wasted words.

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 zero parameters and a rich output schema, the description makes it clear what the tool does and that it's safe to call. The open-world hint implies the output changes based on state, but the description could explicitly state it returns static cached data.

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 coverage is 100% with zero parameters, so the description adds clear value by specifying what will be returned (categories, namespaces, qualifiers, operators, limits) without needing to document parameters.

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 uses specific verbs like "return" and lists concrete resources (categories, namespaces, qualifiers, operators, limits), clearly distinguishing this from sibling tools that perform search queries or fetch external data.

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 explicitly states that no network request is made, which helps agents decide not to use it when real-time data is needed. Adding when to avoid it or a brief alternative mention (e.g., none needed) would push it to a 5.

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