generate_password

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

The description only says 'generate' which implies creation, consistent with readOnlyHint=false, but provides no additional behavioral details such as whether the password is guaranteed to be cryptographically secure, or if any constraints apply.

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, minimal and front-loaded. It could expand slightly to include the configurable nature of the password, but it is not overly verbose.

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?

Without an output schema, the description fails to explain what the tool returns (a string, length, etc.). It also does not mention security level or whether the password meets typical requirements.

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 input schema covers all 5 parameters with descriptions, so the tool description adds no extra information. Baseline score of 3 is appropriate due to high schema coverage.

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 secure password, distinguishing it from siblings like generate_token or generate_uuid. However, it does not specify the exact type of password or additional context like entropy.

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?

No guidance on when to use this tool versus alternatives. For example, if a user needs a random string or token, there is no direction to use other tools like generate_token or generate_uuid.

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