networking_network_latency_calculator

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

The description discloses key behaviors: pure offline math, never pings or contacts hosts, rate-limited (30 req/min), and read-only. It adds beyond annotations (which already declare readOnlyHint, destructiveHint, idempotentHint) by specifying rate limits and the operations' output structure. No contradiction with annotations.

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 well-structured paragraph that front-loads the purpose, then details operations and usage. It is dense with information but could be slightly more concise; however, it avoids fluff and every sentence adds value.

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 tool has three operations, the description covers all modes, explains output for analyze, mentions rate limits and alternatives. With an output schema present, it doesn't need to detail return values. However, it could mention what happens if no input is provided for analyze, so not fully complete.

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. The description adds value by explaining the 'analyze' mode expects latency samples in ms, that non-finite or negative values are invalid, and that 'input' is an alias for 'latencies'. This provides context beyond schema but does not fully detail each parameter's format, so above baseline but not perfect.

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 computes descriptive statistics and performance verdict from latency measurements, and distinguishes three operations (analyze, convert, benchmarks). It explicitly notes it never pings or contacts any host, differentiating it from sibling tools like network_ping or networking_mtu_size_calculator.

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 explicitly tells when to use this tool: for interpreting ping/speedtest samples, and when to use alternative tools (live Ping, Internet Speed Test, MTU Size Calculator). It also mentions rate limits (30 req/min anonymous) and read-only nature, providing clear context for selection.

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