ZoomEye v2 Asset Search

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions automatic Base64 encoding and paid-account requirements but fails to disclose authentication needs, rate limits, pagination behavior, or cost implications. For a search tool, lack of these details reduces transparency.

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 consists of two concise sentences with no redundant information. It is front-loaded with the main action and efficiently covers key points: endpoint, query options, and unsupported APIs.

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 8 parameters (all optional), 100% schema coverage, and presence of an output schema, the description is adequate but not thorough. It explains the query mechanism and scope but omits return format, pagination details, and error handling. For a search tool in a competitive suite, more completeness would be beneficial.

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%, so baseline is 3. The description adds context about the query and qbase64 parameters, explaining the relationship (raw query gets auto-encoded vs. direct base64). This adds marginal value beyond the schema descriptions, which already include examples and defaults.

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 ZoomEye paid-account assets using POST /v2/search, specifying the verb, resource, and API method. It distinguishes from siblings by explicitly noting that free and legacy APIs are not supported, which separates it from related tools like fofa_search or quake_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 provides clear usage guidance: users can either provide a raw query (automatic Base64 encoding) or pass qbase64 directly. It also mentions that free/legacy APIs are not supported, implying when not to use the tool. However, it does not explicitly suggest alternative tools for free or legacy accounts, which would improve clarity.

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