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

With no annotations present, the description carries the full burden of behavioral disclosure. It does this thoroughly: read-only, no tool called, robots.txt honored, no record mutation, rate limited, and contacts an external server on the user's behalf. This gives the agent a clear safety and side-effect profile.

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 four short sentences, each earning its place: main action, read-only confirmation, robots.txt behavior, non-mutation, and rate limiting. It is front-loaded with the core purpose and contains no filler.

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 single-parameter network-probing tool with no output schema, the description covers what it does, what it reports, its safety constraints, and its side-effect boundary. An agent has enough context to decide when to invoke it and what to expect from the result.

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?

The schema already fully documents the single parameter, address, with format and example guidance. The description does not add new parameter-level meaning beyond confirming it is a single https address, so the baseline of 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?

The description uses a specific verb and resource: 'Contact one https address now and report what we see,' followed by the exact three checks it performs. It also distinguishes itself from the broader observatory workflow by stating it does NOT change the published record, which separates it from the next full walk.

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?

It gives clear context: use this for an immediate, one-off live probe of a single address, and explicitly states what it is not for by saying 'This does NOT change the published record - the next full walk does that.' However, it does not explicitly name sibling alternatives like lookup or state for reviewing existing records.

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