Generate passwords into a local file

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

Adds substantial context beyond the annotations: secrets are never returned, never hashed or sampled, and the output file is plaintext rather than a vault. This resolves the natural question of what happens to the generated secret. It stops short of stating what happens if output_path already exists (overwrite vs. refusal), which matters given idempotentHint=false.

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?

Four tight sentences, purpose front-loaded, with the non-obvious constraint (secrets never returned) placed early. Every sentence adds information an agent needs.

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?

No output schema exists, and the description explicitly explains the return behavior (writes to file, never returns secrets), which is the key gap such a tool would otherwise have. For a two-parameter tool with full schema coverage, nothing material is missing.

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%, so baseline is 3, and the description adds real value on top: the 24-character single-password default is not in the schema, and 'Optional bounded local JSON configuration' characterizes config_path's scope better than the schema's field list. It also enforces a usage constraint (never place secrets in arguments).

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?

Names a specific verb and resource ('Generate cryptographically random passwords or EFF-wordlist passphrases') and states the delivery mechanism ('Writes secrets only to a new local .txt file'). No sibling tool does anything similar, and the definition makes the distinction obvious without opening the schema.

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?

Gives concrete operating context: defaults to one 24-character password, optional bounded local JSON config selects settings, and directs the agent to call capabilities for the full list of configuration fields. It lacks explicit when-not guidance, but the tool has no true alternative among the file-processing siblings.

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