Url Status

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

Discloses beyond annotations: does not execute JS, does not bypass access controls, rejects private/SSRF-sensitive URLs. This aligns with readOnlyHint, idempotentHint, and destructiveHint annotations without contradiction.

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 concise sentences with no waste. Each sentence adds essential information: purpose, constraints, and parameter guidance. Front-loaded with the core action.

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 only two parameters, an output schema exists, and comprehensive annotations, the description fully covers usage, constraints, and parameter semantics without gaps.

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% with each parameter described. The description adds value: clarifies url must be absolute public HTTP(S), and explains the fresh parameter's caching behavior, enhancing schema info.

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 checks HTTP reachability, status, and final URL. It specifies use for public HTTP(S) resources, distinguishing it from sibling tools that focus on other aspects like headers, redirects, or security.

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?

Explicitly states when to use (only public HTTP(S)) and when not (no JavaScript, no access controls). Provides guidance on cache usage with the fresh parameter, suggesting default false for reuse.

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