pt_ping

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description usefully adds that every attempt's actual output is retained and that simulated time advances (consistent with a non-read-only, non-idempotent call). It stops short of covering output shape or blocking duration at the max timeout x attempts bound.

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?

Two short sentences front-loaded with the core action and the most surprising behavior (time advancement). The bilingual duplication adds length but is a systemic convention rather than filler prose.

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 4-param tool with full schema coverage, no output schema, and complete annotations, the description supplies the one thing structured data cannot: that results are preserved per attempt and simulation clock advances. Nothing essential to correct invocation is missing.

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 100%, so device/destination/timeout/attempts are already documented. The description adds only a light gloss on attempt semantics ('retain actual output for every attempt') without explaining address-learning retries or timeout interaction beyond 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?

States a specific verb and resource ('Run PC ping') plus two distinctive traits: per-attempt output retention and simulator time advancement. An agent can tell this apart from pt_show/pt_pc_ipconfig, though the description never names a sibling or clarifies the source-device scope explicitly.

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?

Usage is only implied — the mention that it 'advances simulator time while waiting' hints it is a blocking/simulated operation versus pt_fast_forward, but the description never says when to prefer this over pt_show or pt_pc_ipconfig for connectivity checks, nor any exclusions.

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