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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond them: the randomness source is the platform CSPRNG, and entropy in bits is reported. Note the idempotentHint=true annotation is dubious for a random generator, but the description does not contradict it.

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?

Two front-loaded sentences with no filler: capability, variant, reporting, and randomness provenance in minimal space.

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?

With 12 undocumented parameters, a 0% schema coverage, and no usage guidance, the description is far too thin for a tool this configurable. An output schema exists so return values needn't be explained, and entropy is mentioned, but an agent still cannot select or set parameters correctly from this definition.

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 0% across 12 parameters, so neither schema nor description explains any parameter. The description only glancingly implies the 'words' parameter via 'EFF-wordlist passphrases' and hints at entropy; nothing disambiguates the overlapping 'digit' vs 'digits' booleans or the length/words/count/separator/capitalize/excludeAmbiguous options.

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?

Specific verb (generate) plus two concrete resources (cryptographic passwords, EFF-wordlist passphrases) and a stated output artifact (entropy in bits). This clearly separates it from siblings like hash_password, generate_uuid, and generate_totp, which also produce or consume secrets.

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 states what the tool does but never says when to pick it over hash_password/generate_uuid/generate_totp, nor when to choose 'password' vs 'passphrase' style. No prerequisites, exclusions, or alternatives are given.

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