Get popular galleries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds 'current', implying the result set may change over time, which is consistent with idempotency (no side effects, but result may vary). No additional behavioral details (e.g., rate limits, authentication needs) are provided, but annotations carry most of the burden.

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 sentence with no filler, front-loading the verb 'List' and the resource. Every word is informative, and the structure is optimal for quick parsing by an agent.

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 only one parameter, rich annotations, and an output schema (not shown but present), the description is minimally complete. It does not mention result count, ordering, or whether 'popular' refers to a specific time window. The output schema likely covers return structure, but the description lacks some contextual cues that would help an agent anticipate behavior.

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 has 0% property descriptions, so the description must compensate. It mentions 'E-Hentai or ExHentai', which directly explains the sole 'site' parameter's enum values. This adds meaningful semantic context that the raw schema does not provide, though it could be slightly more explicit about the parameter name and default.

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 the specific verb 'List' and the clear resource 'current E-Hentai or ExHentai popular galleries', making the action and scope unambiguous. However, it does not explicitly distinguish this tool from sibling tools like eh_search_galleries, leaving the agent to infer that 'popular' means trending rather than searchable.

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?

No guidance is provided on when to use this tool versus alternatives such as eh_search_galleries or eh_search_favorites. The description simply states functionality without any contextual 'when to use' or 'when not to use' advice, which is insufficient given the large set of sibling tools.

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