IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating this is not a read-only operation (consistent with 'generate' and 'verify'). The description adds context about the dual functionality (hash generation and verification), which isn't covered by annotations. However, it lacks details on performance implications (e.g., bcrypt is computationally expensive), error handling, or output format.

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, efficient sentence that directly states the tool's dual functionality. It's front-loaded with no unnecessary words, making it easy to parse quickly.

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 moderate complexity (dual functionality, security implications) and lack of output schema, the description is minimally adequate. It covers the basic operations but misses context like output format (e.g., returns hash string or verification boolean), security best practices, or error cases (e.g., invalid hash format).

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 100%, with clear parameter descriptions in the schema. The description mentions 'hash' for verification, aligning with the schema, but adds no additional semantic context beyond what's already documented (e.g., how rounds affect security, format of hash output).

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's purpose: 'Generate bcrypt hash or verify password against hash'. It specifies the action (generate/verify) and resource (bcrypt hash/password). However, it doesn't distinguish from sibling tools like hash_md5, hash_sha256, etc., which are also hashing tools but for 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when bcrypt is preferred over other hashing algorithms (e.g., for password storage vs. data integrity), nor does it reference sibling tools like hash_sha256 or generate_password for comparison.

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