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

Neither the description nor annotations disclose important behavioral traits of bcrypt, such as that it is a one-way function, includes a salt, or is intentionally slow to resist brute-force attacks. The description is silent on these critical security aspects.

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 concise sentence, which avoids waste but lacks structure. It fails to front-load key details such as output format or usage context, making it minimally adequate.

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 absence of annotations, output schema, and parameter descriptions, the description must provide substantial context. However, it omits essential details like return value format, security considerations, and the effect of the 'rounds' parameter, leaving the tool severely under-described.

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?

With 0% schema description coverage, the description should explain the role of the 'rounds' parameter (cost factor), but it does not. The description only mentions 'password' without adding any meaning beyond the parameter name.

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 action ('Bcrypt-hash a password') and the intended use ('for storage'), distinguishing it from related tools like bcrypt_verify (verification) and other hash functions (different algorithms).

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?

No guidance is provided on when to use this tool versus alternatives such as bcrypt_verify or other hash tools. The description does not indicate that bcrypt is specifically for password hashing or mention scenarios where it is preferred.

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