arvan_net_ping

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

The description only mentions a system dependency (ping binary) but lacks details about typical side effects, output format, or failure modes. With no annotations providing safety info, the agent is left uncertain about the tool's runtime behavior.

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 concise (one sentence) and front-loaded with the purpose. However, it sacrifices necessary detail, making it borderline under-specified rather than efficiently informative.

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 the simplicity of the tool (2 parameters, no output schema), the description still fails to cover the return value, expected behavior, or parameter semantics. It is too minimal for reliable agent 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?

The input schema has two parameters (host and count) with no schema description, and the tool description fails to explain their meanings or formats. Despite 0% schema coverage, the description provides zero parameter clarification beyond implying 'host' is the target.

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 tool's function as 'ICMP ping a host', specifying both the action (ping) and the resource (host). This verb+resource combination distinguishes it from sibling network tools like DNS lookup or HTTP check.

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 no guidance on when to use this tool versus alternatives such as arvan_net_http_check or arvan_net_tcp_check. It only mentions a prerequisite (ping binary), but does not specify use cases or exclusions.

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