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

With no annotations provided, the description has to disclose behavioral context itself. It adds one useful privacy detail: 'Page content is not stored.' However, it does not say whether the tool makes a network request, follows redirects, or has side effects or rate limits, so the disclosure is meaningful but incomplete.

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 sentences, with the core behavior in the first sentence and the privacy guarantee in the second. It is front-loaded, non-redundant, and every sentence earns its place.

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?

The tool has seven optional parameters, no output schema, and no annotations, and the description does not clarify which parameters are relevant to 'a URL.' It also does not explain what the response structure is or how to handle combinations or omissions of parameters, leaving too much to inference.

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 documents every parameter with 100% coverage, so the baseline is 3. The description adds no additional meaning about how the seven optional parameters relate, which one is primary, or whether multiple parameters can be combined.

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 states a clear result: 'Return host, scheme, and HTTP status for a URL.' This is a specific verb and resource set, so an agent can infer the tool's job. It does not explicitly differentiate the tool from siblings like fetch-status or normalize-url, which also operate on URLs and statuses.

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?

There is no guidance about when to use this tool versus alternatives such as fetch-status, web-fetch, or normalize-url. The description implies a URL-oriented use case but gives no exclusions, prerequisites, or conditions that would help an agent choose confidently.

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