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

No annotations are present, so the description must fully disclose behavior. It mentions 'offline' and 'heuristic' but omits important traits like return format (score/boolean/detail), performance characteristics, or whether it checks against common password lists.

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 very short (two sentences) but contains repetition of 'Offline password strength heuristic.' It could separate purpose from usage more clearly, but it is reasonably concise for a simple tool.

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 and a single parameter, the description should explain what the tool returns (e.g., a score, enum, or text). It fails to do so, leaving the agent guessing about the result format and completeness of the assessment.

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 0% (no descriptions in schema), and the description adds nothing about the 'password' parameter beyond what the schema already indicates (it's a string). The description fails to specify format, constraints, or expected behavior for various inputs.

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 it's an offline password strength heuristic using length, character classes, and common patterns. This distinguishes it from siblings like password_generate or hash functions.

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 explicitly says 'When: Offline password strength heuristic (not a cracker),' providing clear context for when to use it. However, it doesn't exclude alternatives or provide detailed comparison with similar tools.

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