network_ping

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

With no annotations, the description carries the burden. It lists reported metrics (latency, packet loss, TTL, raw ping output) but does not disclose potential side effects, prerequisites, or network implications (e.g., ICMP may be blocked). The optional worker_id behavior is mentioned but not elaborated.

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?

Description is three sentences, mostly efficient. The first sentence 'Menu ID: ping.' is redundant for an AI agent and could be omitted. Core purpose is front-loaded.

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?

Adequate for a simple tool, but gaps exist: no description of output format, error handling, or timeout behavior. The mention of 'raw ping output when available' is vague. With no output schema, more detail would be beneficial.

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 coverage is 100%, so baseline is 3. Description does not add significant meaning beyond the schema; target, packet, and worker_id are already described accurately in the schema.

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?

Description clearly states it tests network connectivity to a hostname/IP and reports latency, packet loss, TTL, and raw ping output. It distinguishes from sibling network tools by specifying 'ping', though it does not explicitly differentiate from similar tools like network_traceroute_stream.

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 on when to use this tool versus alternatives. It mentions using describe_tool for full guidance, but that is not adequate as a usage guideline within the description itself.

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