Internet-wide scan

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds valuable gating information about enterprise access and double confirmation, but does not explain consequences, duration, cost, or rate limits of an internet-wide crawl.

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?

Two short sentences, front-loaded with the enterprise restriction and followed by the confirmation requirements. There is no wasted text.

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?

This is a complex internet-wide crawl operation with four required parameters, no schema descriptions, and no output schema. The description covers eligibility and confirmation but omits critical operational context such as expected runtime, output shape, and usage limits, leaving too much for the agent to infer.

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 carry parameter meaning. It names the target concept ('one port/protocol') and says both confirm flags must be true, but it does not explain what each confirmation flag distinguishes, what protocol strings are valid, or what port values mean beyond the schema's bare integer type.

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 specific verb and resource: 'crawl the Internet for one port/protocol.' The 'Enterprise-only' qualifier and internet-wide scope help distinguish it from targeted scan siblings such as shodan_scan, though no alternative is named explicitly.

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?

It provides an eligibility restriction ('Enterprise-only') and explicit prerequisites ('Requires confirm=true and confirm_internet=true'), which are useful context. However, it does not say when to prefer this over shodan_scan or shodan_search, nor does it state when not to use it.

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