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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds no behavioral context beyond stating the external source 'HackerTarget'. It does not explain what the tool does operationally (e.g., sends ICMP packets, checks host reachability, returns latency metrics) or any limitations. There is no contradiction with annotations, but the description contributes no meaningful 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?

The description is extremely short and front-loaded, but it is under-specified rather than concise. It consists of only three words, which is not enough to convey meaning. This is similar to the calibration example where under-specification receives a score of 2, not 5.

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 a single parameter with no schema description, no output schema, and no sibling differentiation, the description is completely inadequate. It does not explain what the tool does, what input to provide, or what output to expect. Even for a simple tool, this is not enough information for an agent to select and invoke it correctly.

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% and the only parameter 'target' is undefined in both the schema and the description. The description does not clarify whether 'target' is a hostname, IP address, or URL, nor does it explain the expected format or possible values. The description completely fails to compensate for the lack of schema 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 'HackerTarget nping lookup.' is essentially a tautology: it restates the tool name 'nping' and adds the generic verb 'lookup' without specifying what nping does, what resource it targets, or what kind of lookup (e.g., host availability, latency, packet loss). It does not distinguish this tool from network diagnostic siblings like mtr, traceroute, or dns_lookup.

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 versus alternatives. The description provides no context about typical use cases, prerequisites, or exclusions. Sibling tools such as mtr and traceroute exist, but the description gives no basis for choosing nping over them.

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