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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Cancel' implies a mutation operation that stops an ongoing process, but the description doesn't address important behavioral aspects: whether cancellation is reversible, what permissions are required, what happens to partial scan results, or how to verify the scan was running. For a mutation tool with zero annotation coverage, this is inadequate.

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 maximally concise - a single four-word sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple tool with one parameter and clear basic functionality.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address the tool's behavioral implications, error conditions, or relationship to the sibling 'start_scan' tool. The agent would need to guess about important aspects like what constitutes a 'running' scan, cancellation effects, and verification of success.

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?

The schema has 100% description coverage, with the single parameter 'scanId' clearly documented in the schema. The description doesn't add any parameter semantics beyond what's already in the schema, but since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 action ('cancel') and target ('a running scan'), providing specific verb+resource. However, it doesn't differentiate from the sibling tool 'start_scan' beyond the obvious verb difference, missing an opportunity to clarify the relationship between these complementary operations.

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 provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. While the presence of 'start_scan' as a sibling suggests a workflow relationship, the description doesn't explicitly state this or provide any usage context beyond the basic action.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool starts a scan but fails to describe what happens during execution (e.g., whether it runs asynchronously, potential impacts on targets, or expected outputs). This leaves critical behavioral traits undocumented for a tool with security implications.

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 extremely concise with a single, front-loaded sentence ('Start a new nuclei scan') that directly conveys the core purpose without any wasted words. This efficiency makes it easy to parse, though it may lack depth.

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?

Given the tool's complexity (9 parameters, no annotations, no output schema, and security-related functionality), the description is insufficient. It doesn't cover behavioral aspects, output expectations, or usage context, leaving significant gaps for an AI agent to understand how to invoke it correctly and interpret results.

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?

The schema description coverage is 78%, which is relatively high, setting a baseline of 3. The description adds no additional parameter information beyond what the schema provides, such as explaining the relationship between parameters or typical values. It doesn't compensate for the 22% gap in coverage, but the schema handles most documentation.

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 action ('Start a new nuclei scan') with a specific verb ('Start') and resource ('nuclei scan'), making the purpose immediately understandable. However, it doesn't distinguish this from its sibling tool 'cancel_scan' or explain what a 'nuclei scan' entails, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context for initiating a scan. While it implies usage for starting scans, there's no explicit advice on timing, constraints, or how it relates to 'cancel_scan'.

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