ping

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

The description adds minimal behavioral insight beyond what annotations provide (readOnlyHint=false). It does not mention potential firewall blocks, permissions, or that it sends ICMP packets.

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?

Exceptionally concise with two sentences, no extraneous information. Every word serves a purpose.

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 tool with good annotations and full schema coverage, the description is adequate but lacks explanation of return values or output format, given no output schema.

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 covers both parameters (100%). The description provides an example for target, adding marginal value. Baseline 3 is appropriate as it does not significantly enhance understanding beyond 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?

The description clearly states the tool tests network connectivity to a host with a verb-resource pair. It distinguishes from siblings like nslookup (DNS) or curl (HTTP), though it could be more specific about ICMP echo requests.

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 explicit when-to-use or when-not-to-use guidance. The example implies usage for reachability checks but lacks alternatives or context compared to siblings like dig or telnet.

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