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

There are no annotations, so the description carries the full behavioral disclosure burden. It states the core computation and the offline threat model, but does not mention assumptions such as guess-rate, whether the password is transmitted, or behavior with the empty default. For a stateless estimator this is adequate but not rich.

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 a single front-loaded phrase with no filler sentences or unnecessary sections. It loses a point for redundancy: 'Password Entropy:' restates the title, and 'offline' appears twice in 'offline crack time (offline)'.

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?

The output schema covers return structure, but the definition still lacks explicit guidance about the input parameter's meaning and behavior with the empty default. For a security-related tool, it would also be valuable to note whether the password is sent somewhere. The description is enough to attempt a call, but not fully complete.

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%, so the description must compensate for the opaque 'q' parameter. 'Password Entropy' strongly implies that q is the password string, but the mapping is implicit and no format or example is provided. It adds some meaning beyond the schema, but not enough to fully clarify the input contract.

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 names the verb 'Estimate' and the resources 'entropy & offline crack time', making the core purpose clear. The leading 'Password Entropy' narrows the subject to passwords and distinguishes it from generic entropy or string-metric siblings, though it does not explicitly contrast itself with them.

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 purpose implies when to use the tool: when an agent needs a password's entropy or offline crack time. However, it gives no explicit alternatives, exclusions, or conditions, so an agent must infer selection from context rather than being directed.

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