password_generate

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

With no annotations provided, the description discloses a critical behavioral trait: the password is returned in plaintext, which is important for security. It also mentions the need for acknowledgement, but does not cover other behaviors like whether passwords are stored or other side effects.

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 two sentences with no extraneous information. The key purpose and requirements are stated upfront, achieving maximal conciseness.

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 complexity (9 parameters, security-sensitive, no output schema), the description is too brief. It does not explain the return format beyond 'plaintext', lacks details on parameter effects, and provides no information about error cases or storage behavior.

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 schema has 0% description coverage for parameters. The description only mentions 'reason' and 'acknowledgePlaintext' but fails to explain the other 7 parameters (e.g., length, character sets), leaving their semantics unclear.

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 generates a strong random password and returns it in plaintext, which distinguishes it from sibling tools like 'password_generate_memorable' (memorable passwords) and 'password_read' (reading existing passwords).

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 'for immediate use' and that a reason and acknowledgement are required, but it does not explicitly state when not to use this tool or provide alternatives (e.g., using 'password_read' for existing passwords).

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