bulk_hash_lookup

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

No annotations are provided, so the description carries full burden. It discloses validation, backend specifics (Hybrid Analysis, MalwareBazaar), the cap, and a security warning about untrusted data. It lacks details on rate limits or authentication, but the security note adds value.

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, using three short paragraphs. The first sentence front-loads the purpose. Every sentence adds value: validation details, backend info, cap, security note. No redundant or filler 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 the presence of an output schema (which likely explains return values), the description sufficiently covers input, behavior, and security considerations. It is complete for a bulk-lookup tool with one parameter.

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 input schema has 100% coverage with a description for the 'hashes' parameter. The description adds further meaning by specifying accepted hash types (MD5/SHA1/SHA256) and the maximum of 50 processed, which goes beyond the schema.

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 'Look up many file hashes at once across enabled hash-intel backends', specifying the verb and resource. It distinguishes from sibling tools like search_hash (single hash lookup) by emphasizing 'many' and 'at once'.

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 context for when to use (bulk lookup) and explicitly mentions a cap of 50 hashes. However, it does not explicitly state when not to use or name alternatives, though the context of siblings implies it.

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