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

With no annotations provided, the description carries the full burden. It discloses the breach-sourced nature and external source (md5decrypt.net), which is useful context. However, it doesn't mention behavior for unknown hashes, hash format limitations (e.g., unsalted), or whether it's a read-only lookup.

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 compact line with the purpose front-loaded. The parenthetical 'Leaks' and source mention add minor context without bloat. It earns a high score for efficiency.

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's simplicity (one parameter, no required fields) and the existence of an output schema, the description covers the essential usage. The only gap is lack of information about failure behavior, but for a single-query lookup tool this is a minor omission.

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 provides no description for the single parameter 'q' (0% coverage), so the description must compensate. It does by clearly implying the query is the hash to reverse. It doesn't specify formatting details like case or hex requirement, but the core meaning is unambiguous.

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 states a specific verb ('Reverse') and resource ('MD5/SHA1 hash via breach-sourced hash DB'), which clearly identifies the tool's function. It distinguishes itself from sibling hash-related tools like hashid (identification) and sha256lookup (SHA256) by naming the exact hash types and data source.

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 context: use this tool to reverse MD5 or SHA1 hashes using breach-sourced data. It doesn't explicitly name alternatives or exclusions, but the scope is evident enough for an agent to select it over other similar lookup tools.

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