password_generate

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

With no annotations, the description carries the behavioral burden; it reveals that the output is random and cryptographically secure, and implies a stateless, nondestructive operation. It does not specify the exact character set or output framing, but for a generation action the core behavior is still communicated.

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?

One sentence, no wasted words, all relevant information front-loaded. It does not repeat schema details, annotations, or unrelated chatter.

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?

One optional parameter, no nested objects, and simple behavior make the current description + schema enough for most uses. The only minor gap is the exact return formatting is not described, but the meaning of the return value ('password') is obvious from the tool name and description.

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 already provides 100% of parameter semantics, including length range and default. The description itself adds no parameter-specific information, so it hits the baseline without exceeding it.

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 uses a specific verb ('Generate') and a clear resource ('cryptographically secure random password'). It is not a tautology and is clearly distinct from sibling tools like base64_encode, uuid_v4, or timestamp_to_iso.

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 gives clear context: it should be used when a secure random password is needed. It does not name the sibling alternatives or explicitly exclude them, but none of the siblings is a password-generation tool, so the omission is minor.

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