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

The description says the tool generates a 'random' password, which contradicts the provided idempotentHint=true annotation because repeated calls with the same parameters will not produce the same password. This is an Annotation Contradiction. Aside from that, the description mostly restates the schema options and does not disclose return format or other behavioral details.

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 short sentences with no filler. The primary behavior is front-loaded, and the alternative tool is mentioned in a separate concise sentence that adds clear value.

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?

For a simple tool with no required parameters and full schema coverage, the description is mostly sufficient. The main gaps are that it never states the return format (presumably the generated password string) and uses the vague phrase 'reasonable secure length' instead of a concrete default.

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 100%, so the input schema already documents all five parameters. The description only lists the option names without adding types, defaults, or value formats beyond what the schema provides, so it meets the baseline but nothing more.

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 states a specific action and resource: 'Generates a random password'. It also names the option categories (length, symbols, uppercase, numbers, ambiguous characters) and explicitly differentiates the tool from password_check by noting that the latter evaluates 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 second sentence gives an explicit routing rule: use password_check when evaluating an existing password, implying the current tool is for generation. This clearly tells an agent when to choose this tool versus the most relevant sibling.

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