search_vt

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

No annotations provided, so description carries full burden. Discloses query acceptance and pagination, but lacks details on response format, error handling, or rate limits. Adds some context beyond schema.

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?

Two sentences with no wasted words. Front-loaded with purpose in first sentence, second sentence adds valuable details. Ideal conciseness.

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?

No output schema, but description does not hint at return structure (e.g., list of results, count). For a search tool, this is a gap. Adequate for usage guidance but incomplete for full context.

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 33% (only 'query' described briefly). Description adds significant value: explains VTI-style search with examples, mentions cursor for pagination, and reinforces limit behavior. Significantly enriches parameter understanding.

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 it searches the VirusTotal corpus for multiple entity types (files, URLs, domains, IPs, comments) and distinct query styles. It distinguishes from sibling tools, which are all retrieval of specific reports.

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?

Provides explicit guidance on query types (IOCs, free text, VTI modifiers) and pagination via cursor. Does not explicitly state when not to use or compare to alternatives, but context implies search vs. direct lookups.

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