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

Annotations already disclose read-only, non-idempotent, non-destructive behavior. The description adds meaningful context beyond that: each call makes fresh passwords, it specifies the categories and edge cases generated, and it notes the bcrypt 72-byte nuance. It does not contradict the annotations.

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 definition is front-loaded and every major clause contributes a concrete testing rule or usage step. It is dense and written as one long sentence, which slightly hurts scanability, but it does not waste much space on redundant or irrelevant content.

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?

With no output schema, the description still explains that the tool returns categorized passwords (accept, reject, decide) and gives enough context to use them correctly. It does not specify the exact response shape, such as whether passwords are grouped into arrays or objects, but it is otherwise complete for invocation.

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 coverage is 100%, so the schema already documents min_length, max_length, and symbols. The description adds value by explaining how those rules drive generated variants, including exactly-minimum/maximum lengths, symbol-class coverage, and the over-72-byte bcrypt pair.

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 specific verb and resource: it lists passwords for testing an app's password field within that field's rules. It is easy to distinguish from sibling set_password because it generates test variants rather than setting a password, but it never explicitly names or contrasts with sibling tools.

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?

It gives clear usage context: use the generated passwords to test accept/reject/decide behavior, set one with the form, and verify sign-in, including the composed/decomposed accent cross-check. It does not state when not to use it or explicitly name alternatives, so it falls short of a 5.

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