x402node_crypto_pbkdf2

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the basic function (derive key from password using PBKDF2) and configurable parameters, but does not mention whether the operation is deterministic, idempotent, or any security considerations (e.g., salt should be random, iteration counts affect speed). The price note is commercial, not behavioral. Significant gaps remain for a cryptographic tool.

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 relatively short (two sentences plus a price note). The first sentence is a tag list that could be more efficient (redundant synonyms), but the core purpose is front-loaded. The price note is extraneous but brief. Overall, it earns a 4 for being mostly concise with minor fluff.

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 complexity of a cryptographic tool and the absence of an output schema or annotations, the description lacks critical completeness. It does not describe the output format (e.g., hex, base64, raw bytes), any constraints on parameter values, or security warnings. The inclusion of a price note without functional details leaves the agent underinformed for safe and effective use.

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 coverage is 100% with defaults documented, so baseline is 3. The description lists 'configurable iterations, salt, and hash algorithm' but omits 'keylen' and does not explain parameter semantics beyond what the schema already provides. The description adds marginal value by grouping parameters, but fails to fully compensate for the missing output format.

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 identifies the tool as PBKDF2 key derivation and password hashing, listing multiple synonyms (KDF, scrypt alternative, etc.) and explicitly stating it derives a cryptographic key from a password. This distinguishes it from sibling cryptographic tools like AES encryption or HMAC, as none of those perform password-based key derivation.

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 mentions 'scrypt alternative' but provides no explicit guidance on when to use PBKDF2 versus other KDFs or password hashing methods. It does not state when not to use this tool or list alternatives within the toolset. The context is implicit through the tool name and purpose, but lacks explicit why/when-not criteria.

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