run_ncrack

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

No annotations are present, so the description must cover behavioral traits. It only states 'High-speed network authentication cracking,' which implies brute-force attacks but does not disclose potential side effects like rate limits, stealth options, server load, or account lockouts. For a security tool, this is insufficient.

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 sentence with no extraneous words. It is maximally concise and front-loaded with the key information.

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?

Despite having 4 parameters and no output schema, the description is extremely brief. It does not explain the significance of parameters, default values, or how to use them effectively. For a potentially dangerous tool like Ncrack, more context (e.g., warnings, expected outcomes) is needed for safe and correct 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 description coverage is 100%, with each parameter having a basic description. However, the tool description adds no additional meaning beyond these minimal schema comments. For example, 'Comma-separated usernames.' and 'Protocol.' are terse. The description does not provide examples, format details, or usage notes, so it meets the baseline but adds no extra value.

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 'High-speed network authentication cracking' clearly states the tool's purpose with a specific verb and resource. It distinguishes itself from siblings like run_hydra, run_medusa, and run_john by emphasizing 'high-speed' and 'network', though it doesn't explicitly differentiate from hydra/medusa. Still clear enough for an agent to understand the core function.

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?

No guidance is provided on when to use this tool vs alternatives like run_hydra or run_medusa. There are no mentions of prerequisites, when not to use, or typical scenarios. The description offers no context for decision-making.

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