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

With no annotations provided, the description carries the behavioral burden and does disclose a meaningful property: page content is not stored. Still, it omits other relevant behaviors such as whether a network request is made, how redirects or errors are handled, and any rate-limit or privacy implications beyond storage.

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 two short, front-loaded sentences with no filler. It states the core behavior first, then adds a single clarifying privacy note, making it easy for an agent to parse quickly.

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 a nine-parameter optional schema, no annotations, no output schema, and many similar sibling tools, the description is too thin. It does not clarify which parameter an agent should populate for the stated behavior, whether the other parameters are accepted but ignored, or what to pass when only URL status is needed.

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%, so the baseline applies. The input schema already documents every parameter, including which values are discarded. The description adds no parameter-level detail, and the main confusion is that it only mentions URL behavior while the schema exposes many unrelated optional parameters.

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 a specific verb and resource: return host, scheme, and HTTP status for a URL. It distinguishes this tool from content-fetching or normalization siblings by naming concrete outputs rather than merely restating the tool name.

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 the main use case: obtain URL-level metadata without storing page content. However, it does not name alternatives like fetch-status, normalize-url, or web-fetch, nor does it state when those tools should be used instead.

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