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

No annotations are provided, so the description carries the full burden. It discloses that page content is not stored, which is useful, but it fails to mention that many parameters are discarded (as the schema descriptions indicate) or that the tool only returns host, scheme, and HTTP status. The description does not contradict annotations, but it is far too sparse to be transparent for a tool with 9 parameters.

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 a single, front-loaded sentence with no wasted words. It is concise but lacks the context needed for a tool with this many parameters. It earns a 4 because it is structurally efficient, though under-specified.

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?

This tool has 9 optional parameters, no required fields, and no output schema. The description is only one sentence and does not explain the return format beyond 'host, scheme, and HTTP status', nor does it address the role of the other parameters or how they relate to the main purpose. For such complexity, the description is clearly incomplete.

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%, with each parameter having a description (e.g., 'discarded after the shape check'). The tool description adds no extra meaning beyond the schema, so the baseline of 3 is appropriate. The description's focus on URL does not map clearly to the other parameters, but the schema already explains them.

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 specific action: 'Return host, scheme, and HTTP status for a URL.' This is a clear verb+resource combination. However, it does not differentiate from sibling tools like 'fetch-status' or 'normalize-url', and the presence of 9 unrelated optional parameters in the schema muddies the tool's actual scope.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention exclusions or conditions, leaving the agent to guess based on the description alone. The note 'Page content is not stored' is a behavioral statement, not a usage guideline.

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