ip_ping

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly states 'read-only' and specifies '5 packets,' alerting the agent that this is a safe diagnostic operation. It does not mention timeouts or output format, but for a simple ping tool this is adequate.

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 a single, tightly packed phrase with zero filler. It front-loads the action, target, and key behavioral details immediately.

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 diagnostic tool, the description covers the target type, fixed packet count, and read-only nature. There is no output schema, but ping semantics are widely understood; the description is sufficient for selection and invocation.

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 compensate for parameter meaning. 'Ping an IPv4 host' adds little beyond the schema's 'host' property and 'ipv4' format, and the '5 packets' note is behavioral rather than parameter-specific. The parameter semantics remain largely implicit.

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 ('Ping'), the target ('IPv4 host'), and a precise detail ('5 packets'), making the tool's purpose immediately obvious. This also distinguishes it from sibling ip6_ping by explicitly limiting to IPv4.

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 clear context: this is for pinging an IPv4 host, which implies it is the IPv4 counterpart to ip6_ping and distinct from ip_tracert. There is no explicit 'when-not-to-use' statement, but the context is sufficient for a reasonable agent.

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