password

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

The description discloses the use of a CSPRNG and mentions configurable character classes and ambiguous-character exclusion. However, with no annotations, it does not fully carry the burden of behavioral disclosure; it omits return format and edge-case behavior, such as what happens if all character classes are disabled.

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 sentence, front-loaded with the core action. Every word contributes meaning, and there is no redundancy or filler.

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 lack of an output schema and annotations, the description should explain the return value. It does not state whether the tool returns a single string or an array when count > 1, which is essential for an agent to consume the result correctly.

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?

The description summarizes the parameters well, mentioning length, count, character classes, and ambiguous-character exclusion. While the schema has 0% description coverage, the description adds meaning by grouping booleans into 'character classes' but does not detail each parameter individually.

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 it generates cryptographically random passwords, using a specific verb and resource. It implicitly distinguishes itself from sibling tools like password_strength (which analyzes strength) and random_gen (generic random generation).

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 clear context for when to use the tool—whenever a secure random password is needed—but does not explicitly mention alternatives or exclusions. It lacks an explicit statement like 'for password strength checking, use password_strength.'

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