google_image_searchGoogle image search by keyword: return image results (image URL, source link, title). 특정 키워드의 구글 이미지 검색 결과(이미지 URL·출처 링크·제목)를 조회합니다. page 로 결과 페이지를 넘겨 가며 조회할 수 있습니다. [호출당 20포인트]
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 검색 결과 조회 페이지 (기본값 1) | |
| keyword | Yes | 검색할 키워드 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations give readOnlyHint and openWorldHint, and the description adds specific return fields, pagination usage, and the per-call cost of 20 points. This provides useful behavioral context beyond the annotations without 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?
The description is concise and front-loaded with the core purpose, then adds pagination and cost. It repeats the same message in English and Korean, which adds length without new information, but this may serve a bilingual audience.
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?
For a simple read-only tool with two parameters and no output schema, the description sufficiently covers expected return values, pagination, and cost, enabling an agent to invoke 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?
Schema description coverage is 100%, so the parameters are already well-documented. The description's mention of page pagination reinforces but does not significantly augment the schema's own description, yielding only marginal added semantics.
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?
Description states the specific verb 'search by keyword', the resource 'Google image', and the output fields 'image URL, source link, title'. The word 'image' clearly separates it from generic google_search and google_lens_search.
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 clearly implies usage for keyword-based Google image searches and explains pagination via the 'page' parameter. It does not explicitly exclude alternatives or compare with sibling tools, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action or resource: YouTube has crawl and download; Google has three separate search modes; URL tools cover HTML fetching, screenshots, and similarity; and network tools are all unique lookups. No two tools overlap in purpose, making selection unambiguous.
The naming is generally readable but mixes conventions: some use verb_noun (crawl_youtube, reverse_ip), others use noun_noun with brand prefixes (google_search, url_screenshot), and a few are single conventional words (location, whois, nslookup). While not chaotic, there is no uniform verb_noun pattern across the set.
With 13 tools, the server is well-scoped for a web research/investigation toolkit. Each tool covers a distinct aspect of web data collection and DNS/IP analysis, and none feel redundant or unnecessary.
The toolkit provides comprehensive coverage for web research: searching (web, image, reverse image), YouTube data collection, URL content analysis, and a full suite of DNS/IP/WHOIS tools. There are no obvious dead ends or missing operations for its intended purpose.