run_netscan

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, and the description adds the permission requirement 'requires write permission', which is useful behavioral context. However, it does not disclose side effects, duration, or asynchronicity, leaving room for more transparency.

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?

A single, front-loaded sentence contains the core purpose and a critical precondition ('requires write permission'). No filler or redundant phrasing, making it highly efficient.

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 simple one-parameter tool with no output schema, the minimal description is adequate. However, it omits what happens after execution (e.g., whether results are returned, if the scan is asynchronous, or how to check status), so an agent cannot fully anticipate the next steps.

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% coverage for the only parameter (netscan_id) with description 'Netscan ID to run'. The tool description adds no further meaning beyond the schema, so 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 states a clear action and resource: 'Execute a network scan'. It distinguishes from sibling read tools like get_netscan/get_netscans by using 'execute' rather than 'get'. However, it does not explicitly contrast with any sibling, leaving some ambiguity about the exact scope of the operation.

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?

There is no guidance on when to use this tool. It does not mention that one must first list available netscans via get_netscans or that results can be retrieved via get_netscan. The description simply states the action without context or alternatives.

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