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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine scope behavior beyond that — a 20-link ceiling, same-origin filtering, and per-link status reporting — but says nothing about redirect handling, blocked/failed link behavior, or how long a run may take.

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, zero filler, and the scope constraint leads before the exclusion. Nothing repeats the name or title verbatim.

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 one-parameter read-only tool with no output schema and full annotation coverage, the description conveys the essentials: what is checked, the boundary of the check, and that statuses are returned per link. Only the target format and failure/redirect semantics are 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?

The single 'target' parameter has 0% schema description coverage, so the description carries the burden. 'Found on one page' implies target is a page URL, which is useful, but it gives no format guidance (scheme required? path allowed? origin vs full URL) for a 1–1024 char string.

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 ('Check ... links found on one page and report the status of each') plus concrete scope limits: up to 20 links, same-origin only. The explicit 'not a site crawl' line separates it from crawl-style siblings, but it never distinguishes itself from the closest alternative, check_http_status.

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?

One negative exclusion is given ('This is a single page check, not a site crawl'), which implies when to reach for it, but no sibling is named as the alternative and no prerequisite (reachable page, same-origin assumption) is stated. Usage is inferable rather than spelled out.

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