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

With no annotations, the description carries the full burden and does well: it discloses the threat model (offline attack at 10^10 guesses/s), the privacy guarantee ('evaluated in memory only, never stored or logged'), and the commercial cost (x402 $0.01/call, USDC on eip155:8453). It does not describe rate limits or the exact response shape, which is a real but modest gap.

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 methodology and usage clause are front-loaded and useful, but the sentence is overloaded with em-dashes and parentheticals, and 'the honest math behind "is this password good?"' is marketing filler that consumes space without informing invocation.

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?

No annotations and no output schema, so the description must stand alone — it names the computed components (entropy bits, crack-time estimate, pattern detection) and the privacy/cost behavior. What it lacks is any indication of the returned payload's structure, which matters more because no output schema exists.

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?

One required parameter with 100% schema description coverage (though the schema text is merely 'Password'), so the baseline is 3. The description implies the input is a plaintext password processed in memory but adds no format, length, or charset constraints beyond that.

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?

Specific verb+resource ('Scores a password') followed by the exact methodology (character-pool size, length, offline crack-time at 10^10 guesses/s, pattern detection). An agent can immediately distinguish this from neighbors like security_cvss_calc or security_totp_generator without opening a schema.

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?

'Use this when an agent needs entropy bits + realistic crack-time estimate' gives clear positive usage context. It stops short of exclusions or naming alternatives, but no sibling performs password-strength scoring, so the routing risk is low.

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