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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely new behavioral context: the probe is a single HTTPS HEAD request issued from the server edge, not a full download or a device-side measurement, which materially changes how results should be interpreted. It omits anything about rate limits or failure behavior, keeping it just short of a 5.

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?

Front-loaded with the core definition in the first sentence, followed by the disambiguation. The closing sentence ('These paths and results are different') largely restates the preceding one and could be cut, and 'esimgomobile' appears to be a garbled reference.

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?

With a rich annotation set, a fully documented single parameter, and an output schema, the description only needs to explain what is being measured and from where — which it does. The remaining gap is the lack of guidance relative to sibling diagnostic tools like run_speed_test.

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% and the single parameter is already documented with an example format. The description contributes only a mild constraint via 'public host,' implying the destination must be publicly reachable. Otherwise the schema does the work, so baseline 3 applies.

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: measures an HTTPS HEAD request from the server edge to a public host. It explicitly distinguishes this from browser-based measurement done by the separate website tool. It does not, however, differentiate itself from siblings like run_speed_test or grade_connection_quality, which an agent could reasonably confuse with this.

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 implied by the contrast with browser-based timing ('server edge ... not from the user device'), which hints at when this tool is the right choice. But there is no explicit when-to-use/when-not statement, and no sibling is named as an alternative — the comparison is to an unnamed external website tool.

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