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

The annotations declare openWorldHint=false, but the description says the tool performs an HTTPS probe against a public domain, which is an external, open-world interaction. That is a direct inconsistency with the annotation, so this dimension is capped at 1 despite the otherwise useful return-shape and billing details.

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 compact and front-loaded: it states the core probe, defines the returned fields and edge semantics, then gives billing and validation behavior. Every sentence carries useful information without padding.

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?

There is no output schema, but the description explicitly explains the return shape and the meaning of up and status, as well as billing and schema-validation behavior. For a two-parameter read-only probe, that gives an agent enough information to call and interpret it correctly.

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%, and the schema already documents domain and path constraints, including allowed path characters, length limits, and private-suffix refusal. The description adds little parameter-level meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 names a specific action and resource: one HTTPS probe of a public domain, returning status, latency, and lookup result. It is clear what the tool does, but it does not explicitly distinguish itself from nearby network siblings such as http-status, dns-lookup, or https-redirect.

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 implies a quick uptime/status probe, but gives no explicit when-to-use or when-not-to-use guidance. With many network-related sibling tools available, an agent is left to infer why this should be chosen over http-status, dns-lookup, or header-audit.

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