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

With no annotations, the description carries the full disclosure burden. It does reveal one meaningful behavioral trait: 'Page content is not stored.' It also states the output fields. However, it omits other useful behavioral details such as redirect handling, validation behavior, failure modes, or any network/privacy implications beyond page content 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?

Two short sentences with no filler. The primary output is stated first, and the important side-effect note is second. Every word 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?

Given the unusual nine-parameter schema and the presence of many similarly named sibling tools, the description is not complete enough. It does not explain why so many unrelated parameters exist, which parameter is actually required for the described behavior, or how this tool differs from fetch-status and normalize-url. The lack of an output schema also makes the minimal return-field list important, but it is not expanded with examples or edge cases.

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 is 3. The description does not add meaningful parameter guidance beyond the schema; it only mentions 'URL,' which is already covered by the url parameter description. It does not help clarify the role of the many seemingly 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 states a specific action and output: 'Return host, scheme, and HTTP status for a URL.' This clearly identifies the resource and result. It does not explicitly distinguish it from siblings like fetch-status or normalize-url, but the core purpose is understandable.

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 usage context is provided. There is no guidance on when to prefer this tool over fetch-status, normalize-url, browser-url-ok, or other sibling tools. 'Page content is not stored' hints at a privacy-relevant use case, but it is not developed into concrete when-to-use guidance.

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